pub struct ValueInThread<T> {
value: T,
_in_thread: InThread,
}
Expand description
A value combined with an InThread
marker
This does barely implement anything on its own, but the module implementing T
might provide
extra methods.
This makes the wrapped value not Send
.
Fields§
§value: T
§_in_thread: InThread
Implementations§
Source§impl<T> ValueInThread<T>
impl<T> ValueInThread<T>
Sourcepub fn into_inner(self) -> T
pub fn into_inner(self) -> T
Extract the wrapped value
This does not produce the original in_thread
value; these are easy enough to re-obtain or
to keep a copy of around.
Source§impl<const HZ: u32> ValueInThread<Clock<HZ>>
impl<const HZ: u32> ValueInThread<Clock<HZ>>
Sourcepub fn sleep(&self, duration: Ticks<HZ>)
Available on riot_module_ztimer
only.
pub fn sleep(&self, duration: Ticks<HZ>)
riot_module_ztimer
only.Pause the current thread for the duration of ticks in the timer’s time scale.
Wraps ztimer_sleep
Sourcepub fn spin(&self, duration: Ticks<HZ>)
Available on riot_module_ztimer
only.
pub fn spin(&self, duration: Ticks<HZ>)
riot_module_ztimer
only.Keep the current thread in a busy loop until the duration of ticks in the timer’s tim scale has passed
Quoting the original documentation, “This blocks lower priority threads. Use only for very short delays.”.
Wraps ztimer_spin
Note that this would not technically require the self to be a ValueInThread (as spinning is doable in an ISR), but it’s so discouraged that the Rust wrapper takes the position that it’s best done using a ValueInThread.
Sourcepub fn sleep_extended(&self, duration: Duration)
Available on riot_module_ztimer
only.
pub fn sleep_extended(&self, duration: Duration)
riot_module_ztimer
only.Pause the current thread for the given duration, possibly exceeding values expressible in
Ticks<HZ>
.
The duration is converted into ticks (rounding up), and overflows are caught by sleeping multiple times.
It is up to the caller to select the Clock suitable for efficiency. (Even sleeping for seconds on the microseconds timer would not overflow the timer’s interface’s u32, but the same multiple-sleeps trick may need to be employed by the implementation, and would keep the system from entering deeper sleep modes).
Sourcepub fn set_during<I: FnOnce() + Send, M: FnOnce() -> R, R>(
&self,
callback: I,
ticks: Ticks<HZ>,
in_thread: M,
) -> R
Available on riot_module_ztimer
only.
pub fn set_during<I: FnOnce() + Send, M: FnOnce() -> R, R>( &self, callback: I, ticks: Ticks<HZ>, in_thread: M, ) -> R
riot_module_ztimer
only.Set the given callback to be executed in an interrupt some ticks in the future.
Then, start the in_thread function from in the thread this is called from (as a regular function call).
After the in_thread function terminates, the callback is dropped if it has not already triggered.
Further Development:
-
This could probably be done with some sort of pinning instead, thus avoiding the nested scope – but getting the Drop right is comparatively tricky, because when done naively it needs runtime state.
-
The callback could be passed something extra that enables it to set the timer again and again. Granted, there’s ztimer_periodic for these cases (and it has better drifting properties), but for something like exponential retransmission it could be convenient.
(Might make sense to do this without an extra function variant: if the callback ignores the timer argument and always returns None, that’s all in the caller type and probebly inlined right away).
While (unless with sleep) nothing would break if this were called from an interrupt
context, it would not work either: As RIOT uses flat interrupt priorities, any code
executed in the in_thread
handler would still be run in the original interrupt, and while
the configured ZTimer would fire its interrupt during that time, the interrupt would not be
serviced, and the timer would be removed already by the time the original interrupt
completes and ZTimer is serviced (finding no actually pending callback).
Source§impl<'a, T> ValueInThread<&'a Mutex<T>>
impl<'a, T> ValueInThread<&'a Mutex<T>>
Sourcepub fn lock(self) -> MutexGuard<'a, T>
pub fn lock(self) -> MutexGuard<'a, T>
Get an accessor to the mutex when the mutex is available
Through the crate::thread::ValueInThread, this is already guaranteed to run in a thread context, so no additional check is performed.
Trait Implementations§
Source§impl<T: Clone> Clone for ValueInThread<T>
impl<T: Clone> Clone for ValueInThread<T>
Source§fn clone(&self) -> ValueInThread<T>
fn clone(&self) -> ValueInThread<T>
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl<const F: u32> DelayNs for ValueInThread<Clock<F>>
Available on riot_module_ztimer
only.
impl<const F: u32> DelayNs for ValueInThread<Clock<F>>
riot_module_ztimer
only.Source§fn delay_ns(&mut self, ns: u32)
fn delay_ns(&mut self, ns: u32)
ns
nanoseconds. Pause can be longer
if the implementation requires it due to precision/timing issues.Source§impl<T> Deref for ValueInThread<T>
impl<T> Deref for ValueInThread<T>
Source§impl<T> DerefMut for ValueInThread<T>
impl<T> DerefMut for ValueInThread<T>
impl<T: Copy> Copy for ValueInThread<T>
Auto Trait Implementations§
impl<T> Freeze for ValueInThread<T>where
T: Freeze,
impl<T> RefUnwindSafe for ValueInThread<T>where
T: RefUnwindSafe,
impl<T> !Send for ValueInThread<T>
impl<T> !Sync for ValueInThread<T>
impl<T> Unpin for ValueInThread<T>where
T: Unpin,
impl<T> UnwindSafe for ValueInThread<T>where
T: UnwindSafe,
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> IntoSwitch for T
impl<T> IntoSwitch for T
Source§fn into_switch<ActiveLevel>(self) -> Switch<T, ActiveLevel>
fn into_switch<ActiveLevel>(self) -> Switch<T, ActiveLevel>
Source§fn into_active_high_switch(self) -> Switch<Self, ActiveHigh>where
Self: Sized,
fn into_active_high_switch(self) -> Switch<Self, ActiveHigh>where
Self: Sized,
Layout§
Note: Unable to compute type layout, possibly due to this type having generic parameters. Layout can only be computed for concrete, fully-instantiated types.