Help¶

System clock source is initiated but does not wait for clock readiness. When this option is picked, system clock may not be ready when code relying on kernel API is executed. Requested timeouts will be prolonged by the remaining startup time.

Direct dependencies¶

<choice: Clock startup policy>

(Includes any dependencies from ifs and menus.)

Kconfig definition¶

At <Zephyr>/drivers/timer/Kconfig:164

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:32 → <Zephyr>/drivers/Kconfig:28

Menu path: (Top) → Device Drivers → Timer Drivers → nRF Real Time Counter (NRF_RTC1) Timer → Clock startup policy

config SYSTEM_CLOCK_NO_WAIT
    bool "No wait"
    depends on <choice: Clock startup policy>
    help
      System clock source is initiated but does not wait for clock readiness.
      When this option is picked, system clock may not be ready when code relying
      on kernel API is executed. Requested timeouts will be prolonged by the
      remaining startup time.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)