:orphan:

.. title:: CONFIG_TICKLESS_CAPABLE

.. kconfig:: CONFIG_TICKLESS_CAPABLE

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
===============================

- \ :kconfig:`NRF_TIMER_TIMER <CONFIG_NRF_TIMER_TIMER>`
- \ :kconfig:`APIC_TIMER <CONFIG_APIC_TIMER>`
- \ :kconfig:`APIC_TSC_DEADLINE_TIMER <CONFIG_APIC_TSC_DEADLINE_TIMER>`
- \ :kconfig:`HPET_TIMER <CONFIG_HPET_TIMER>`
- \ :kconfig:`ARCV2_TIMER <CONFIG_ARCV2_TIMER>`
- \ :kconfig:`ARM_ARCH_TIMER <CONFIG_ARM_ARCH_TIMER>`
- \ :kconfig:`CORTEX_M_SYSTICK <CONFIG_CORTEX_M_SYSTICK>`
- \ :kconfig:`ITE_IT8XXX2_TIMER <CONFIG_ITE_IT8XXX2_TIMER>`
- \ :kconfig:`NRF_RTC_TIMER <CONFIG_NRF_RTC_TIMER>`
- \ :kconfig:`RISCV_MACHINE_TIMER <CONFIG_RISCV_MACHINE_TIMER>`
- \ :kconfig:`NATIVE_POSIX_TIMER <CONFIG_NATIVE_POSIX_TIMER>`
- \ :kconfig:`XTENSA_TIMER <CONFIG_XTENSA_TIMER>`
- \ :kconfig:`ESP32C3_SYS_TIMER <CONFIG_ESP32C3_SYS_TIMER>`
- \ :kconfig:`SAM0_RTC_TIMER <CONFIG_SAM0_RTC_TIMER>`
- \ :kconfig:`MCHP_XEC_RTOS_TIMER <CONFIG_MCHP_XEC_RTOS_TIMER>`
- \ :kconfig:`CC13X2_CC26X2_RTC_TIMER <CONFIG_CC13X2_CC26X2_RTC_TIMER>`
- \ :kconfig:`XLNX_PSTTC_TIMER <CONFIG_XLNX_PSTTC_TIMER>`
- \ :kconfig:`CAVS_TIMER <CONFIG_CAVS_TIMER>`
- \ :kconfig:`NPCX_ITIM_TIMER <CONFIG_NPCX_ITIM_TIMER>`
- \ :kconfig:`MCUX_OS_TIMER <CONFIG_MCUX_OS_TIMER>`

Kconfig definition
==================



At ``<Zephyr Driver>/timer/Kconfig:388``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:42`` → ``<Zephyr Driver>/Kconfig:30``

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