:orphan:

.. title:: CONFIG_ARCH_HAS_CUSTOM_BUSY_WAIT

.. kconfig:: CONFIG_ARCH_HAS_CUSTOM_BUSY_WAIT

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

Symbols that select this symbol
===============================

- \ :kconfig:`ARCH_POSIX <CONFIG_ARCH_POSIX>`
- \ :kconfig:`ARM_ARCH_TIMER <CONFIG_ARM_ARCH_TIMER>`

Kconfig definitions
===================



At ``<Zephyr SoC>/arm/microchip_mec/mec1501/Kconfig.defconfig.series:27``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:25`` → ``<BuildDir>/kconfig/Kconfig.soc.defconfig:1`` → ``<Zephyr SoC>/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 ``<Zephyr SoC>/arm/microchip_mec/mec172x/Kconfig.defconfig.series:27``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:25`` → ``<BuildDir>/kconfig/Kconfig.soc.defconfig:1`` → ``<Zephyr SoC>/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_MEC172X

----

At ``<Zephyr SoC>/arm/nordic_nrf/Kconfig.defconfig:27``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:25`` → ``<BuildDir>/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 ``<Zephyr SoC>/arm/microchip_mec/mec1501/Kconfig.defconfig.series:27``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:27`` → ``<Zephyr SoC>/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 ``<Zephyr SoC>/arm/microchip_mec/mec172x/Kconfig.defconfig.series:27``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:27`` → ``<Zephyr SoC>/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_MEC172X

----

At ``<Zephyr SoC>/arm/nordic_nrf/Kconfig.defconfig:27``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:27``

Menu path: (Top)

.. code-block:: kconfig

    config ARCH_HAS_CUSTOM_BUSY_WAIT
    	bool
    	default y
    	depends on SOC_FAMILY_NRF

----

At ``<Zephyr Kernel>/Kconfig:554``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:40``

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