diff options
| author | kalkyl <[email protected]> | 2024-07-08 22:53:50 +0200 |
|---|---|---|
| committer | kalkyl <[email protected]> | 2024-07-08 22:53:50 +0200 |
| commit | af9c7379f99b309a99b0b573ebfb8ea1bebecaf9 (patch) | |
| tree | 7160def9d4b71c014f0279917bbdab0e035f5e22 /docs | |
| parent | 03f3a3389d0691492e5d60cd243f3287a4ab42b8 (diff) | |
Add link to example in book
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/pages/sharing_peripherals.adoc | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/docs/pages/sharing_peripherals.adoc b/docs/pages/sharing_peripherals.adoc index ebd899c4e..6ba13f93b 100644 --- a/docs/pages/sharing_peripherals.adoc +++ b/docs/pages/sharing_peripherals.adoc | |||
| @@ -127,4 +127,8 @@ async fn toggle_led(control: Sender<'static, ThreadModeRawMutex, LedState, 64>, | |||
| 127 | This example replaces the Mutex with a Channel, and uses another task (the main loop) to drive the LED. The advantage of this approach is that only a single task references the peripheral, separating concerns. However, using a Mutex has a lower overhead and might be necessary if you need to ensure | 127 | This example replaces the Mutex with a Channel, and uses another task (the main loop) to drive the LED. The advantage of this approach is that only a single task references the peripheral, separating concerns. However, using a Mutex has a lower overhead and might be necessary if you need to ensure |
| 128 | that the operation is completed before continuing to do other work in your task. | 128 | that the operation is completed before continuing to do other work in your task. |
| 129 | 129 | ||
| 130 | An example showcasing more methods for sharing link:https://github.com/embassy-rs/embassy/blob/main/examples/rp/src/bin/sharing.rs[can be found here]. \ No newline at end of file | 130 | An example showcasing more methods for sharing link:https://github.com/embassy-rs/embassy/blob/main/examples/rp/src/bin/sharing.rs[can be found here]. |
| 131 | |||
| 132 | == Sharing an I2C or SPI bus between multiple devices | ||
| 133 | |||
| 134 | An example of how to deal with multiple devices sharing a common I2C or SPI bus link:https://github.com/embassy-rs/embassy/blob/main/examples/rp/src/bin/shared_bus.rs[can be found here]. | ||