Expand description
§Atomic locks for Raspberry Pi baremetal systems
This crate provides different kinds of locks and access guards to secure data access across cores and/or threads.
Those locks are Spinlock, Semaphore, Mutex and RWLock. The * Semaphore*, Mutex and RWLock are available
as async
version as well to allow them to work in a non blocking fashion as required by async
code.
§Usage Hint:
As the locks depend on low level atomics they do only work on the Raspberry Pi if the MMU is properly configured. Otherwise using either of the lock functions will hang the core it has been used on.
§Features
Feature | Usage |
---|---|
async_locks | allows usage of the async lock versions. |
To share those locking primitives accross the Rasperry Pi cores they should be wrapped in an Arc
.
§Usage
§Spinlock
use ruspiro_lock::sync::Spinlock;
fn main() {
let spin = Spinlock::new();
spin.aquire();
// following code is only executed if the lock could be aquired, the executing core pause till then
let _ = 10 + 3;
spin.release();
}
§Semaphore
use ruspiro_lock::sync::Semaphore;
fn main() {
let sema = Semaphore::new(1);
if sema.try_down().is_ok() {
// we gained access to the semaphore, do something
let _ = 20 /4;
sema.up();
}
}
§Mutex
use ruspiro_lock::sync::Mutex;
fn main() {
let mutex = Mutex::new(0u32);
if let Some(mut data) = mutex.try_lock() {
*data = 20;
}
// once the data goes ot of scope the lock will be released
if let Some(data) = mutex.try_lock() {
println!("data: {}", *data);
// another lock should fail inside this scope
assert!(mutex.try_lock().is_none());
}
// a blocking lock on the data will block the current execution until the lock get's available
let mut data = mutex.lock();
*data = 12;
}
Re-exports§
pub use sync::*;
Modules§
- Async Locking
- Sync Locking