:orphan: .. title:: ARCH_HAS_CUSTOM_BUSY_WAIT .. option:: CONFIG_ARCH_HAS_CUSTOM_BUSY_WAIT *(No prompt -- not directly user assignable.)* Type: ``bool`` Help ==== .. code-block:: none It's possible that an architecture port cannot or does not want to use the provided k_busy_wait(), but instead must do something custom. It must enable this option in that case. Defaults ======== - y - y Symbols that select this symbol =============================== - \ :option:`ARCH_POSIX ` - \ :option:`ARM_ARCH_TIMER ` Kconfig definitions =================== At ``/arm/microchip_mec/mec1501/Kconfig.defconfig.series:27`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:19`` → ``/kconfig/Kconfig.soc.defconfig:1`` → ``/arm/microchip_mec/Kconfig.defconfig:3`` Menu path: (Top) .. code-block:: kconfig config ARCH_HAS_CUSTOM_BUSY_WAIT bool default y depends on RTOS_TIMER && SOC_SERIES_MEC1501X ---- At ``/arm/nordic_nrf/Kconfig.defconfig:27`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:19`` → ``/kconfig/Kconfig.soc.defconfig:1`` Menu path: (Top) .. code-block:: kconfig config ARCH_HAS_CUSTOM_BUSY_WAIT bool default y depends on SOC_FAMILY_NRF ---- At ``/Kconfig:546`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:30`` Menu path: (Top) → General Kernel Options .. code-block:: kconfig config ARCH_HAS_CUSTOM_BUSY_WAIT bool help It's possible that an architecture port cannot or does not want to use the provided k_busy_wait(), but instead must do something custom. It must enable this option in that case. *(The 'depends on' condition includes propagated dependencies from ifs and menus.)*