CONFIG_ARCH_HAS_CUSTOM_BUSY_WAIT

(No prompt – not directly user assignable.)

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

Defaults

y
y
y
y
y
y

Symbols that select this symbol

Kconfig definitions

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

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:25 → <nRF>/doc/_build/kconfig/Kconfig.soc.defconfig:1 → <Zephyr>/soc/arm/microchip_mec/Kconfig.defconfig:3

Menu path: (Top)

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 <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:25 → <nRF>/doc/_build/kconfig/Kconfig.soc.defconfig:1 → <Zephyr>/soc/arm/microchip_mec/Kconfig.defconfig:3

Menu path: (Top)

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 <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:25 → <nRF>/doc/_build/kconfig/Kconfig.soc.defconfig:1

Menu path: (Top)

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 <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:27 → <Zephyr>/soc/arm/microchip_mec/Kconfig.defconfig:3

Menu path: (Top)

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 <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:27 → <Zephyr>/soc/arm/microchip_mec/Kconfig.defconfig:3

Menu path: (Top)

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 <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:27

Menu path: (Top)

config ARCH_HAS_CUSTOM_BUSY_WAIT
    bool
    default y
    depends on SOC_FAMILY_NRF

At <Zephyr>/kernel/Kconfig:577

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:40

Menu path: (Top) → General Kernel Options

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