Lines Matching refs:timer

113   within another timer's callback will always be calculated with a precise offset
114   to the firing timer. It is thereby possible to fire at regular intervals without
168 Kernel timing at the tick level is driven by a timer driver with a
199 kernel, which receives and processes timer interrupts only for
219 In general, the timer API described above does not change when run in
224 * Zephyr is agnostic about which CPU services timer interrupts.  It is
226   have every timer interrupt handled on a single processor.  Existing
227   SMP architectures implement symmetric timer drivers.
231   per-CPU tracking, and expects that if two timer interrupts fire near
237 * Some SMP hardware uses a single, global timer device, others use a
244   So by default, every CPU will see simultaneous timer interrupts for
251   responsibility of the timer driver.
263 Zephyr multiplexes the existing timer driver.  This means that the