diff options
| author | Ulf Lilleengen <[email protected]> | 2025-01-02 12:03:03 +0100 |
|---|---|---|
| committer | Ulf Lilleengen <[email protected]> | 2025-01-02 12:03:03 +0100 |
| commit | 06901c3279430a40a449e5944e8ba3788388deb7 (patch) | |
| tree | 65d9f67ed80e79972c00269b511e87731838693d | |
| parent | 9c7d508bcf3384ab0883c7ef710e485106ccbb6c (diff) | |
Update comment to reflect reality
| -rw-r--r-- | embassy-nrf/src/time_driver.rs | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/embassy-nrf/src/time_driver.rs b/embassy-nrf/src/time_driver.rs index ad61f5ca7..b8c19014e 100644 --- a/embassy-nrf/src/time_driver.rs +++ b/embassy-nrf/src/time_driver.rs | |||
| @@ -231,9 +231,9 @@ impl RtcDriver { | |||
| 231 | // To workaround this, we never write a timestamp smaller than N+3. | 231 | // To workaround this, we never write a timestamp smaller than N+3. |
| 232 | // N+2 is not safe because rtc can tick from N to N+1 between calling now() and writing cc. | 232 | // N+2 is not safe because rtc can tick from N to N+1 between calling now() and writing cc. |
| 233 | // | 233 | // |
| 234 | // It is impossible for rtc to tick more than once because | 234 | // Since the critical section does not guarantee that a higher prio interrupt causes |
| 235 | // - this code takes less time than 1 tick | 235 | // this to be delayed, we need to re-check how much time actually passed after setting the |
| 236 | // - it runs with interrupts disabled so nothing else can preempt it. | 236 | // alarm, and retry if we are within the unsafe interval still. |
| 237 | // | 237 | // |
| 238 | // This means that an alarm can be delayed for up to 2 ticks (from t+1 to t+3), but this is allowed | 238 | // This means that an alarm can be delayed for up to 2 ticks (from t+1 to t+3), but this is allowed |
| 239 | // by the Alarm trait contract. What's not allowed is triggering alarms *before* their scheduled time, | 239 | // by the Alarm trait contract. What's not allowed is triggering alarms *before* their scheduled time, |
