aboutsummaryrefslogtreecommitdiff
path: root/examples/stm32h7/src/bin/signal.rs
Commit message (Collapse)AuthorAgeFilesLines
* executor: return error when creating the spawntoken, not when spawning.Dario Nieuwenhuis2025-08-291-1/+1
|
* ci: use beta, add secondary nightly ci.Dario Nieuwenhuis2023-12-211-1/+0
|
* time: Update examples, tests, and other code to use new Timer::after_x ↵Adam Greig2023-10-151-2/+2
| | | | convenience methods
* Remove default, reorder generic paramsivmarkov2022-09-251-1/+2
|
* sync: flatten module structure.Dario Nieuwenhuis2022-08-221-1/+1
|
* split `embassy-util` into `embassy-futures`, `embassy-sync`.Dario Nieuwenhuis2022-08-221-1/+1
|
* Split embassy-time from embassy-executor.Dario Nieuwenhuis2022-08-181-2/+2
|
* Remove HAL initialization from #[embassy::main] macro.Dario Nieuwenhuis2022-08-171-2/+2
|
* Split embassy crate into embassy-executor, embassy-util.Dario Nieuwenhuis2022-07-291-5/+5
|
* Run rustfmt.Dario Nieuwenhuis2022-06-121-6/+1
|
* Rename channel to mpmchuntc2022-06-121-1/+1
| | | | I've renamed the channel module for the MPMC as mpmc. There was a previous debate about this, but I feel that the strategy here avoids importing `channel::channel`. The change leaves `signal::Signal`, but I think that's ok. It is all a bit subjective of course. The bottom line for me is that I really like the term mpmc - it means something to me and aligns with broader naming e.g. in Tokio.
* Add example for using a Signal.Dominic Clifton2022-06-061-0/+41