-
Notifications
You must be signed in to change notification settings - Fork 219
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
ClockSource: should this be non-exhaustive?
1.0-blocker
peripheral:uart
UART peripheral
#2735
opened Dec 10, 2024 by
MabezDev
Uart constructor should take pins via the builder lite pattern
1.0-blocker
peripheral:uart
UART peripheral
#2734
opened Dec 10, 2024 by
MabezDev
AtCmdConfig
should be #[non_exaustive]
1.0-blocker
peripheral:uart
#2733
opened Dec 10, 2024 by
MabezDev
AtCmdConfig
should be a part of Config
1.0-blocker
peripheral:uart
#2732
opened Dec 10, 2024 by
MabezDev
Allow enabling/disabling cts/rts via UART peripheral
Config
1.0-blocker
peripheral:uart
#2731
opened Dec 10, 2024 by
MabezDev
Should uart use UART peripheral
nb
types and implementations?
1.0-blocker
peripheral:uart
#2730
opened Dec 10, 2024 by
MabezDev
Missing UART peripheral
read_byte
that doesn't use nb
1.0-blocker
peripheral:uart
#2729
opened Dec 10, 2024 by
MabezDev
Should split halves be allowed to be in different UART peripheral
Mode
s?
1.0-blocker
peripheral:uart
#2728
opened Dec 10, 2024 by
MabezDev
Should split halves have individual constructors?
1.0-blocker
peripheral:uart
UART peripheral
#2727
opened Dec 10, 2024 by
MabezDev
AtCmdConfig
should use the builder-lite pattern instead of that constructor
1.0-blocker
peripheral:uart
#2726
opened Dec 10, 2024 by
MabezDev
fill_fifo
seems redundant vs read_bytes
1.0-blocker
peripheral:uart
#2725
opened Dec 10, 2024 by
MabezDev
ConfigError: should be non-exhaustive
1.0-blocker
peripheral:uart
UART peripheral
#2724
opened Dec 10, 2024 by
MabezDev
[RMT] Allow reading of more data than fits into the peripheral's allocated RAM
status:needs-attention
This should be prioritized
#2723
opened Dec 10, 2024 by
alexstephanus
Re-use WiFi/BLE calibration result
status:needs-attention
This should be prioritized
#2720
opened Dec 10, 2024 by
maufl
GPIO: GPIO peripheral
C-CUSTOM-TYPE
1.0-blocker
peripheral:gpio
#2715
opened Dec 9, 2024 by
bugadani
GPIO documentation issue: GPIO peripheral
C-QUESTION-MARK
1.0-blocker
peripheral:gpio
#2714
opened Dec 9, 2024 by
bugadani
GPIO: If a common Instance trait is used for multiple peripherals, those traits should not have any logic implemented in them.
1.0-blocker
peripheral:gpio
GPIO peripheral
#2713
opened Dec 9, 2024 by
bugadani
GPIO: If a driver only implements a subset of a peripheral's capabilities, it should be placed in the GPIO peripheral
peripheral::subcategory
module.
1.0-blocker
peripheral:gpio
#2712
opened Dec 9, 2024 by
bugadani
GPIO: Avoiding GPIO peripheral
&mut self
when &self
is safe to use.
1.0-blocker
peripheral:gpio
#2711
opened Dec 9, 2024 by
bugadani
GPIO: Prefer compile-time checks over runtime checks where possible, prefer a fallible API over panics.
1.0-blocker
peripheral:gpio
GPIO peripheral
#2710
opened Dec 9, 2024 by
bugadani
GPIO: If a driver implements both blocking and async operations, or only implements blocking operations, but may support asynchronous ones in the future, the driver's type signature must include a GPIO peripheral
crate::Mode
type parameter.
1.0-blocker
peripheral:gpio
#2709
opened Dec 9, 2024 by
bugadani
GPIO: The driver's constructor should take the config struct by value, and it should return GPIO peripheral
Result<Self, ConfigError>
1.0-blocker
peripheral:gpio
#2708
opened Dec 9, 2024 by
bugadani
GPIO: The author must to use GPIO peripheral
crate::any_peripheral
to define the "any" peripheral instance type.
1.0-blocker
peripheral:gpio
#2707
opened Dec 9, 2024 by
bugadani
Document using peripheral drivers in generic contexts
1.0-blocker
documentation
Improvements or additions to documentation
#2706
opened Dec 9, 2024 by
bugadani
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.