mirror of
https://github.com/apache/nuttx.git
synced 2026-09-02 07:03:04 +00:00
cb5bab34f1
Now we have CONFIG_USEC_PER_TICK, and for our timer system, all the calculation used 'tick'. And all the timespec should change to 'tick' before use wd_start(), so USEC2TICK() can NOT be avoided. Then there must be an 'less then one tick' loss. One resolution: ticks++ anyway when wd_start(). But this will caused time expired more a tick. Another resolution: Change the testcase, and allow the following logic: t1 = current_time(); sleep(3); t2 = current_time(); allow: t2 - t1 >= 3; (original test must be: t2- t1 > 3) The original test think the time must be elapse-ing, and the (t2 - t1) must bigger then 3, but in our system, we use 'tick' as the minimal wdog unit, then there must a precision loss. Now we choose first resolution. Signed-off-by: ligd <liguiding1@xiaomi.com> |
||
|---|---|---|
| .. | ||
| addrenv | ||
| clock | ||
| environ | ||
| event | ||
| group | ||
| init | ||
| instrument | ||
| irq | ||
| misc | ||
| module | ||
| mqueue | ||
| paging | ||
| pthread | ||
| sched | ||
| semaphore | ||
| signal | ||
| task | ||
| timer | ||
| tls | ||
| wdog | ||
| wqueue | ||
| CMakeLists.txt | ||
| Kconfig | ||
| Makefile | ||