This test sets a timer, busy waits for half the duration, and then checks the remaining time is correct. And it correctly does all its math in tick precision and aligns to a timer interrupt to eliminate aliasing due to the tick stride. But it's waiting using k_busy_wait(), not a timer: "half the duration" in MICROSECONDS (for k_busy_wait()) is not necessarily representable as an integer number of TICKS on all platforms. Because k_busy_wait() always rounds up, we need one extra tick of buffer on those platforms. Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
|---|---|---|
| .. | ||
| starve | ||
| timer_api | ||
| timer_monotonic | ||