mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-08 12:52:42 +00:00
Our funny convention holds that passing ticks==1 to _add_timeout() means "at the next tick". But that means that 1, 0, and all negative numbers are expected to behave the same. In ticked mode, that's fine because it will, after all, expire at the next tick. But in tickless, the next announcement may be for several ticks, and that zero will appear to expire "before" the next tick in the consumption loop. Make sure all "next tick" expirations look the same. Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
---|---|---|
.. | ||
include | ||
alert.c | ||
atomic_c.c | ||
CMakeLists.txt | ||
compiler_stack_protect.c | ||
device.c | ||
errno.c | ||
idle.c | ||
init.c | ||
int_latency_bench.c | ||
Kconfig | ||
Kconfig.power_mgmt | ||
mailbox.c | ||
mem_domain.c | ||
mem_slab.c | ||
mempool.c | ||
msg_q.c | ||
mutex.c | ||
pipes.c | ||
poll.c | ||
queue.c | ||
sched.c | ||
sem.c | ||
smp.c | ||
stack.c | ||
system_work_q.c | ||
thread_abort.c | ||
thread.c | ||
timeout.c | ||
timer.c | ||
userspace_handler.c | ||
userspace.c | ||
version.c | ||
work_q.c |