833: nrf/uart: add support for tx-only and rx-only uart. r=Dirbaio a=Dirbaio
Allow creating UarteRx/UarteTx directly. This allows using uart unidirectionally
(rx-only or tx-only), without having to 'waste' a pin for the unused direction.
Co-authored-by: Dario Nieuwenhuis <dirbaio@dirbaio.net>
Allow creating UarteRx/UarteTx directly. This allows using uart unidirectionally
(rx-only or tx-only), without having to 'waste' a pin for the unused direction.
828: More API docs r=lulf a=lulf
embassy-cortex-m is covered now, making some progress on embassy-nrf, but not complete.
Co-authored-by: Ulf Lilleengen <lulf@redhat.com>
827: Fix PWM for advanced timers r=Dirbaio a=chemicstry
Advanced timers have additional BDTR register, which has a global output enable bit and it is disabled by default.
Also added an example for F4, but it will only work once https://github.com/embassy-rs/stm32-data/pull/149 is merged. We can also move it to some other chip, but I don't have anything else to test on atm.
Co-authored-by: chemicstry <chemicstry@gmail.com>
805: Preliminary Xtensa support r=Dirbaio a=MabezDev
Based on the work in #804.
I hope non-upstream target support is acceptable :).
Co-authored-by: Scott Mabin <scott@mabez.dev>
825: Fixed a pubsub mutability inconsistency r=lulf a=diondokter
All other publish methods don't require mut
Co-authored-by: Dion Dokter <diondokter@gmail.com>
- Adds a executor for the Xtensa arch
- Light sleep implemented with assembly, so we don't pull in the
xtensa_lx crates (yet)
- lock behind a nightly feature due to Xtensa asm support not upstream
817: Added a pubsub channel implementation r=lulf a=diondokter
This is similar to Tokio's Broadcast channel, except that it doesn't allocate.
The publishers and subscribers are dynamic. They use an &dyn channel reference because it's really annoying to have to specify the mutex and const generics every time.
Do we need fully generic types as well?
Co-authored-by: Dion Dokter <diondokter@gmail.com>
Co-authored-by: Dion Dokter <dion@tweedegolf.com>
It currently contains whoever was first to write some code for the crate,
even if many more people have contributed to it later.
The field is "sort of" deprecated, it was made optional recently:
https://rust-lang.github.io/rfcs/3052-optional-authors-field.html
Due the the reasons listed there I believe removing it is better than
setting it to generic fluff like "The Embassy contributors".
