The latest development version of this page may be more current than this released 2.7.5 version.

CONFIG_TICKLESS_CAPABLE

(No prompt – not directly user assignable.)

Type: 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.

Defaults

No defaults. Implicitly defaults to n.

Symbols that select this symbol

• NRF_TIMER_TIMER

• APIC_TIMER

• APIC_TSC_DEADLINE_TIMER

• HPET_TIMER

• ARCV2_TIMER

• ARM_ARCH_TIMER

• CORTEX_M_SYSTICK

• ITE_IT8XXX2_TIMER

• NRF_RTC_TIMER

• RISCV_MACHINE_TIMER

• NATIVE_POSIX_TIMER

• XTENSA_TIMER

• ESP32C3_SYS_TIMER

• SAM0_RTC_TIMER

• MCHP_XEC_RTOS_TIMER

• CC13X2_CC26X2_RTC_TIMER

• XLNX_PSTTC_TIMER

• CAVS_TIMER

• NPCX_ITIM_TIMER

• MCUX_OS_TIMER

Kconfig definition

At drivers/timer/Kconfig:388

Included via Kconfig:8 → Kconfig.zephyr:42 → drivers/Kconfig:30

Menu path: (Top) → Device Drivers → Timer Drivers

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.)