You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[list of features]: https://twitter.com/therealjpster/status/1055187256091332608
63
63
64
-
## Peripheral Ownership Woes? Not with`shared-bus`!
64
+
## Peripheral Ownership Woes? Not With`shared-bus`!
65
65
66
66
<hr>
67
67
@@ -87,10 +87,10 @@ let port_b = Pcf8574(manager.acquire(), 0x38).unwrap();
87
87
88
88
In most `embedded-hal` compatible drivers, the driver takes either ownership or a mutable reference to the peripheral used to interact with a component, such as I2C or SPI. For some protocols, such as I2C, which might have multiple devices connected to the same peripheral, managing ownership can be difficult (see [embedded-hal/35] for discussion).
89
89
90
-
To address this, [@rahix] developed [shared-bus], a crate which provides safe shared access to these peripherals through the use of a mutex. This allows for access of the underlying peripheral in as many drivers as you need! Check out the [release blog post] for more details, and for examples on how to use this for your projects.
90
+
To address this, [@Rahix] developed [shared-bus], a crate which provides safe shared access to these peripherals through the use of a mutex. This allows for access of the underlying peripheral in as many drivers as you need! Check out the [release blog post] for more details, and for examples on how to use this for your projects.
* Interested in implementing a new target for Embedded Rust? Nuvoton has a [development board] for the Cortex-M23. Check out the [thumbv8m tracking issue] if you want to help!
0 commit comments