a1d21ca69b
If the timer driver only implements sys_clock_cycle_get_32() (meaning CONFIG_TIMER_HAS_64BIT_CYCLE_COUNTER=n) and the hardware clock is high enough then the reported cycle count may wrap an uint32_t during the test. This makes validating the total test duration pointless as it cannot be measured. Just print a warning instead of failing the test in that case. Signed-off-by: Nicolas Pitre <npitre@baylibre.com> |
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| Kconfig | ||
| prj.conf | ||
| README | ||
| testcase.yaml | ||
# Test a timer implementations variance and long term drift Records and calculates statistical values against a timer validating that. 1. Timer variance and standard deviation is below defined acceptable values. 2. Periodic timers do not drift in either direction from expected total time. Timers are meant to be precise and accurate. This test validates an implementation is both.