Struct riot_wrappers::ztimer::Clock
source · pub struct Clock<const HZ: u32>(/* private fields */);
riot_module_ztimer
only.Expand description
A clock that knows about its frequency. The pulse length is not given in core::time::Duration as that’s not yet supported by const generics, and because clock rates are often easier to express in Hertz than in multiples of 10^-n seconds.
Implementations§
source§impl<const HZ: u32> Clock<HZ>
impl<const HZ: u32> Clock<HZ>
sourcepub fn sleep_ticks(&self, duration: u32)
pub fn sleep_ticks(&self, duration: u32)
Pause the current thread for the duration of ticks in the timer’s time scale.
Wraps ztimer_sleep
sourcepub fn spin_ticks(&self, duration: u32)
pub fn spin_ticks(&self, duration: u32)
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
sourcepub fn sleep(&self, duration: Duration)
pub fn sleep(&self, duration: Duration)
Pause the current thread for the given duration.
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 async fn sleep_async(&self, duration: Ticks<HZ>)
pub async fn sleep_async(&self, duration: Ticks<HZ>)
Similar to [sleep_ticks()
], but this does not block but creates a future to be
.await
ed.
Note that time starts running only when this is polled, for otherwise there’s no pinned Self around.
sourcepub fn set_during<I: FnOnce() + Send, M: FnOnce() -> R, R>(
&self,
callback: I,
ticks: Ticks<HZ>,
in_thread: M
) -> R
pub fn set_during<I: FnOnce() + Send, M: FnOnce() -> R, R>( &self, callback: I, ticks: Ticks<HZ>, in_thread: M ) -> R
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).
Trait Implementations§
source§impl<const F: u32> DelayNs for Clock<F>
impl<const F: u32> DelayNs for Clock<F>
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.