Skip to content

Issues: esp-rs/esp-hal

Stable driver analysis tracking issue
#2491 opened Nov 8, 2024 by MabezDev
Open 6
Mark unstable APIs
#2499 opened Nov 8, 2024 by MabezDev
Open
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

254 Open 762 Closed
254 Open 762 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

ESP32S3 ADC reading not working as expected bug Something isn't working status:needs-attention This should be prioritized
#2815 opened Dec 13, 2024 by DS204ever
We do not distinguish NACK sources (address/data) which embedded-hal supports. Adding this would change the Error type, most likely renaming the AckCheckFailed variant. 1.0-blocker peripheral:i2c I2C peripheral
#2814 opened Dec 13, 2024 by bugadani
Wake-up (e.g. light sleep) 1.0-blocker peripheral:uart UART peripheral
#2813 opened Dec 13, 2024 by bugadani
C-FAILURE: Function docs include error, panic, and safety considerations 1.0-blocker peripheral:uart UART peripheral
#2812 opened Dec 13, 2024 by bugadani
C-QUESTION-MARK: Examples use ?, not try!, not unwrap 1.0-blocker peripheral:uart UART peripheral
#2811 opened Dec 13, 2024 by bugadani
C-COMMON-TRAITS 1.0-blocker peripheral:uart UART peripheral
#2810 opened Dec 13, 2024 by bugadani
Allow using SPI1, if we can automatically handle its specific requirements: driver must be in IRAM, interrupt handlers must either be masked or be in IRAM, GPIO assignment (probably?) needs to be restored after use. 1.0-blocker peripheral:spi SPI peripheral
#2809 opened Dec 13, 2024 by bjoernQ
1
Do we want the single byte read/write inherent functions? or are they optimized for the job and are much more efficient? is it a common use case? 1.0-blocker peripheral:spi SPI peripheral
#2808 opened Dec 13, 2024 by bjoernQ
Should we get rid of nb::Result for inherent functions? 1.0-blocker peripheral:spi SPI peripheral
#2807 opened Dec 13, 2024 by bjoernQ
SpiBitOrder, SpiDataMode, SpiMode: the Spi prefix seems redundant 1.0-blocker peripheral:spi SPI peripheral
#2805 opened Dec 13, 2024 by bjoernQ
spi::master::Config uses HertzU32 etc from fugit, which aren't stable 1.0-blocker peripheral:spi SPI peripheral
#2804 opened Dec 13, 2024 by bjoernQ
Expose Double Transfer Rate where supported 1.0-blocker peripheral:spi SPI peripheral
#2803 opened Dec 13, 2024 by bjoernQ
Ability to transfer bit arrays (data that is not a multiple of 8 bits). 1.0-blocker peripheral:spi SPI peripheral
#2802 opened Dec 13, 2024 by bjoernQ
SPI: Expose timing delays 1.0-blocker peripheral:spi SPI peripheral
#2801 opened Dec 13, 2024 by bjoernQ
Allow using the RX half and TX half in different (CPU/DMA) modes (Sometimes you only really need DMA in one half of the SPI transfer. This one might be difficult to support) 1.0-blocker peripheral:spi SPI peripheral
#2800 opened Dec 13, 2024 by bjoernQ
Expose SPI interrupts 1.0-blocker peripheral:spi SPI peripheral
#2799 opened Dec 13, 2024 by bjoernQ
Allow splitting the SPI FiFo into two halves (All chips support doing this, and it allows for double buffering without DMA) 1.0-blocker peripheral:spi SPI peripheral
#2798 opened Dec 13, 2024 by bjoernQ
Expose the KEEP_CS_ACTIVE option (This is important for chunked transfers in a single transaction) 1.0-blocker peripheral:spi SPI peripheral
#2797 opened Dec 13, 2024 by bjoernQ
CS timings 1.0-blocker peripheral:spi SPI peripheral
#2796 opened Dec 13, 2024 by bjoernQ
Expose all the CS signals (The SPI hardware can take multiple CS pins and turn them on/off for each transfer. Software CS shouldn't be the long term solution for shared buses) 1.0-blocker peripheral:spi SPI peripheral
#2795 opened Dec 13, 2024 by bjoernQ
SPI: C-FAILURE: Function docs include error, panic, and safety considerations. (again, good in Safety, but Errors and Panics are missing. 1.0-blocker peripheral:spi SPI peripheral
#2794 opened Dec 13, 2024 by bjoernQ
SPI: We already started marking parts of the driver as unstable but there are some inconsistencies currently 1.0-blocker peripheral:spi SPI peripheral
#2793 opened Dec 13, 2024 by bjoernQ
SPI: Config doesn't derive Hash 1.0-blocker peripheral:spi SPI peripheral
#2792 opened Dec 13, 2024 by bjoernQ
SPI: Driver structs don't derive PartialEq/Eq 1.0-blocker peripheral:spi SPI peripheral
#2791 opened Dec 13, 2024 by bjoernQ
C-FAILURE: Function docs include error, panic, and safety considerations. 1.0-blocker peripheral:i2c I2C peripheral
#2789 opened Dec 13, 2024 by bugadani
ProTip! no:milestone will show everything without a milestone.