-
Notifications
You must be signed in to change notification settings - Fork 2.1k
cpu/nrf5x: clean up periph_uart #20102
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
Conversation
fc9bd78
to
fa66a61
Compare
I can test it on nRF53 too probably tonight or tomorrow if you want. |
That would be awesome! Thx 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nRF53 shell still works and changes looks good to me.
Seems like |
Indeed. But at least the I'll fix and squash when the kids are asleep :-) |
fa66a61
to
a8eb54d
Compare
a8eb54d
to
f2e1e4e
Compare
f2e1e4e
to
91c40ed
Compare
Now at least locally all boards build |
- nRF51: Use `uart_conf_t` for consistency with nRF52 - nRF52832: Use UARTE (UART with EasyDMA) over UART (without DMA), as done for all other nRF52 family members - use `UARTE_PRESENT` to detect whether an UARTE can be used, rather than family names
Fixes the "comma should be followed by whitespace" warning from `static-tests`.
91c40ed
to
a28003f
Compare
And the usual forgot about KConfig issue 😅 |
🎉 thx :-) |
Contribution description
uart_conf_t
for consistency with nRF52UARTE_PRESENT
to detect whether an UARTE can be used, rather than family namesTesting procedure
UART should still work on
nrf51-dk
)nrf52840-dk
)nrf52-dk
)Issues/PRs references
None