Home
last modified time | relevance | path

Searched full:wakes (Results 1 – 25 of 35) sorted by relevance

12

/Zephyr-latest/tests/kernel/context/
DKconfig5 int "Maximum number of spurious wakes during k_cpu_idle() test"
10 running causing the CPU to awake. With this option we allow for a maximum number of wakes
/Zephyr-latest/boards/native/nrf_bsim/
Dcpu_wait.c32 * There may be wakes due to other interrupts or nested calls to in arch_busy_wait()
57 * There may be wakes due to other interrupts or nested calls to in posix_cpu_hold()
Dirq_handler.c94 /* "spurious" wakes can happen with interrupts locked */ in posix_irq_handler()
/Zephyr-latest/boards/native/native_posix/
Dcpu_wait.c40 * There may be wakes due to other interrupts including in arch_busy_wait()
65 * There may be wakes due to other interrupts or nested calls to in posix_cpu_hold()
Dirq_handler.c75 /* "spurious" wakes can happen with interrupts locked */ in posix_irq_handler()
/Zephyr-latest/boards/native/native_sim/
Dcpu_wait.c43 * There may be wakes due to other interrupts including in arch_busy_wait()
68 * There may be wakes due to other interrupts or nested calls to in posix_cpu_hold()
Dirq_handler.c76 /* "spurious" wakes can happen with interrupts locked */ in posix_irq_handler()
/Zephyr-latest/tests/kernel/mutex/sys_mutex/src/
Dmain.c28 * - 0.5 sec: thread_09 wakes and waits on mutex_1
30 * - 1.5 sec: thread_08 wakes and waits on mutex_2
32 * - 2.5 sec: thread_07 wakes and waits on mutex_3
34 * - 3.5 sec: thread_05 wakes and waits on mutex_4
35 * - 3.5 sec: thread_11 wakes and waits on mutex_3
36 * - 3.75 sec: thread_06 wakes and waits on mutex_4
37 * - 4.0 sec: main thread wakes (@ priority 5) then sleeps
39 * - 5.0 sec: main thread wakes (@ priority 6) then gives mutex_4
/Zephyr-latest/drivers/bbram/
DKconfig.stm3216 by system reset or when the device wakes up from Standby mode. They are
/Zephyr-latest/dts/bindings/memory-controllers/
Dst,stm32-bbram.yaml10 by system reset or when the device wakes up from Standby mode. They are
/Zephyr-latest/tests/benchmarks/latency_measure/
DREADME.rst86 …events.post.immediate.kernel - Post events (nothing wakes) : …
87 …events.set.immediate.kernel - Set events (nothing wakes) : …
139 …events.post.immediate.kernel - Post events (nothing wakes) : …
140 …events.set.immediate.kernel - Set events (nothing wakes) : …
196 …events.post.immediate.kernel - Post events (nothing wakes) : …
197 …events.set.immediate.kernel - Set events (nothing wakes) : …
292 …events.post.immediate.kernel - Post events (nothing wakes) : …
293 …events.set.immediate.kernel - Set events (nothing wakes) : …
296 …events.post.immediate.user - Post events (nothing wakes) : …
297 …events.set.immediate.user - Set events (nothing wakes) : …
/Zephyr-latest/samples/boards/nxp/mimxrt595_evk/system_off/
DREADME.rst60 eXecutes-In-Place (XIP) from the external flash. When the MCU wakes from
61 DPD, it wakes through the reset flow. But if the external flash is not
/Zephyr-latest/samples/sensor/isl29035/
DREADME.rst16 application wakes, displays the intensity, resets the intensity range
/Zephyr-latest/include/zephyr/drivers/mfd/
Dnpm2100.h94 * Enters low power state, and wakes after specified time or "shphld" pin signal.
Dnpm1300.h132 * Enters low power state, and wakes after specified time
/Zephyr-latest/tests/boards/intel_adsp/smoke/src/
Dhostipc.c87 * completion and make sure the interrupt fires and wakes us in ZTEST()
/Zephyr-latest/subsys/pm/
DKconfig126 the core wakes up from low power mode all suspended devices
/Zephyr-latest/samples/userspace/prod_consumer/
DREADME.rst41 When it wakes up, copy the data payload into a buffer allocated out
/Zephyr-latest/tests/benchmarks/latency_measure/src/
Devents.c202 "%-40s - Post events (nothing wakes)", tag); in event_ops()
215 "%-40s - Set events (nothing wakes)", tag); in event_ops()
/Zephyr-latest/tests/lib/c_lib/thrd/src/
Dcnd.c82 /* re-signal so that the next thread wakes up too */ in test_cnd_thread_fn()
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dcore.rst17 LPN. The LPN saves power by keeping its radio turned off, and only wakes up to
/Zephyr-latest/dts/bindings/sensor/
Dti,tmag5170.yaml33 automatically wakes up to take another sample. The sleep time is determined
/Zephyr-latest/include/zephyr/pm/
Dpm.h131 * those cases, the ISR would be invoked immediately after the event wakes up
/Zephyr-latest/doc/services/input/
Dgpio-kbd.rst43 keys are released, and the keyboard matrix thread only wakes up when a key has
/Zephyr-latest/drivers/bluetooth/hci/
Dhci_ambiq.c210 /* The controller sends NOP event when wakes up based on in bt_hci_evt_recv()

12