-
Notifications
You must be signed in to change notification settings - Fork 221
Issues: esp-rs/esp-hal
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
parl_io: max dma size should be 65536 based on the register field PARL_IO_TX_BYTELEN
bug
Something isn't working
status:needs-attention
This should be prioritized
#2861
opened Dec 21, 2024 by
liebman
Peripheral drivers should validate configuration before applying it to hardware
bug
Something isn't working
status:needs-attention
This should be prioritized
#2839
opened Dec 19, 2024 by
bugadani
Investigate C-INTERMEDIATE for all stabilized drivers
1.0-blocker
investigation
Not needed for 1.0, but don't know if we can support without breaking the driver.
#2820
opened Dec 16, 2024 by
bugadani
Memory leak when writing to BleConnector
bug
Something isn't working
status:needs-attention
This should be prioritized
#2816
opened Dec 13, 2024 by
s8alprys
Wake-up (e.g. light sleep)
1.0 non-breaking
Not needed for 1.0 and can be supported without breaking the driver.
peripheral:uart
UART peripheral
#2813
opened Dec 13, 2024 by
bugadani
C-FAILURE: Function docs include error, panic, and safety considerations
1.0 non-breaking
Not needed for 1.0 and can be supported without breaking the driver.
documentation
Improvements or additions to documentation
peripheral:uart
UART peripheral
#2812
opened Dec 13, 2024 by
bugadani
C-QUESTION-MARK: Examples use ?, not try!, not unwrap
1.0 non-breaking
Not needed for 1.0 and can be supported without breaking the driver.
peripheral:uart
UART peripheral
#2811
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 non-breaking
Not needed for 1.0 and can be supported without breaking the driver.
peripheral:spi
SPI peripheral
#2809
opened Dec 13, 2024 by
bjoernQ
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
investigation
Not needed for 1.0, but don't know if we can support without breaking the driver.
peripheral:spi
SPI peripheral
#2808
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
investigation
Not needed for 1.0, but don't know if we can support without breaking the driver.
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 non-breaking
Not needed for 1.0 and can be supported without breaking the driver.
peripheral:spi
SPI peripheral
#2802
opened Dec 13, 2024 by
bjoernQ
SPI: Expose timing delays
1.0-blocker
investigation
Not needed for 1.0, but don't know if we can support without breaking the driver.
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
investigation
Not needed for 1.0, but don't know if we can support without breaking the driver.
peripheral:spi
SPI peripheral
#2800
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
investigation
Not needed for 1.0, but don't know if we can support without breaking the driver.
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
investigation
Not needed for 1.0, but don't know if we can support without breaking the driver.
peripheral:spi
SPI peripheral
#2797
opened Dec 13, 2024 by
bjoernQ
CS timings
1.0-blocker
investigation
Not needed for 1.0, but don't know if we can support without breaking the driver.
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
investigation
Not needed for 1.0, but don't know if we can support without breaking the driver.
peripheral:spi
SPI peripheral
#2795
opened Dec 13, 2024 by
bjoernQ
SPI: Not needed for 1.0 and can be supported without breaking the driver.
documentation
Improvements or additions to documentation
peripheral:spi
SPI peripheral
C-FAILURE
: Function docs include error, panic, and safety considerations. (again, good in Safety
, but Errors
and Panics
are missing.
1.0 non-breaking
#2794
opened Dec 13, 2024 by
bjoernQ
C-FAILURE: Function docs include error, panic, and safety considerations.
1.0 non-breaking
Not needed for 1.0 and can be supported without breaking the driver.
documentation
Improvements or additions to documentation
peripheral:i2c
I2C peripheral
#2789
opened Dec 13, 2024 by
bugadani
C-VALIDATE
1.0-blocker
investigation
Not needed for 1.0, but don't know if we can support without breaking the driver.
peripheral:i2c
I2C peripheral
#2787
opened Dec 13, 2024 by
bugadani
Previous Next
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.