:orphan: .. title:: TICKLESS_CAPABLE .. option:: CONFIG_TICKLESS_CAPABLE *(No prompt -- not directly user assignable.)* Type: ``bool`` Help ==== .. code-block:: none Timer drivers should select this flag if they are capable of supporting tickless operation. That is, a call to sys_clock_set_timeout() with a number of ticks greater than one should be expected not to produce a call to sys_clock_announce() (really, not to produce an interrupt at all) until the specified expiration. Defaults ======== No defaults. Implicitly defaults to ``n``. Symbols that select this symbol =============================== - \ :option:`NRF_TIMER_TIMER ` - \ :option:`APIC_TIMER ` - \ :option:`APIC_TSC_DEADLINE_TIMER ` - \ :option:`HPET_TIMER ` - \ :option:`ARCV2_TIMER ` - \ :option:`ARM_ARCH_TIMER ` - \ :option:`CORTEX_M_SYSTICK ` - \ :option:`ITE_IT8XXX2_TIMER ` - \ :option:`NRF_RTC_TIMER ` - \ :option:`STM32_LPTIM_TIMER ` - \ :option:`RISCV_MACHINE_TIMER ` - \ :option:`NATIVE_POSIX_TIMER ` - \ :option:`XTENSA_TIMER ` - \ :option:`SAM0_RTC_TIMER ` - \ :option:`MCHP_XEC_RTOS_TIMER ` - \ :option:`CC13X2_CC26X2_RTC_TIMER ` - \ :option:`XLNX_PSTTC_TIMER ` - \ :option:`CAVS_TIMER ` - \ :option:`NPCX_ITIM_TIMER ` - \ :option:`MCUX_OS_TIMER ` Kconfig definition ================== At ``/timer/Kconfig:379`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:32`` → ``/Kconfig:28`` Menu path: (Top) → Device Drivers → Timer Drivers .. code-block:: kconfig config TICKLESS_CAPABLE bool help Timer drivers should select this flag if they are capable of supporting tickless operation. That is, a call to sys_clock_set_timeout() with a number of ticks greater than one should be expected not to produce a call to sys_clock_announce() (really, not to produce an interrupt at all) until the specified expiration. *(The 'depends on' condition includes propagated dependencies from ifs and menus.)*