mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-06 09:41:56 +00:00
The k_timer utility was written to assume that the kernel timeout handler would never be delayed by more than a tick, so it can naively reschedule the next interrupt with a simple delay. Unfortunately real platforms have glitchy hardware and high tick rates, and on intel_adsp we're seeing this promise being broken in some circumstances. It's probably not a good idea to try to plumb the timer driver interface up into the IPC layer to do this correction, but thankfully the existing absolute timeout API provides the tools we need (though it does require that CONFIG_TIMEOUT_64BIT be enabled). Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
---|---|---|
.. | ||
include | ||
paging | ||
atomic_c.c | ||
banner.c | ||
cache_handlers.c | ||
CMakeLists.txt | ||
compiler_stack_protect.c | ||
condvar.c | ||
device.c | ||
errno.c | ||
events.c | ||
fatal.c | ||
futex.c | ||
idle.c | ||
init.c | ||
Kconfig | ||
Kconfig.vm | ||
kheap.c | ||
mailbox.c | ||
main_weak.c | ||
mem_domain.c | ||
mem_slab.c | ||
mempool.c | ||
mmu.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.c | ||
timeout.c | ||
timer.c | ||
usage.c | ||
userspace_handler.c | ||
userspace.c | ||
version.c | ||
work.c | ||
xip.c |