Home
last modified time | relevance | path

Searched refs:wake (Results 1 – 25 of 95) sorted by relevance

1234

/Zephyr-latest/samples/boards/espressif/deep_sleep/
DREADME.rst4 Use deep sleep with wake on timer, GPIO, and EXT1 sources on ESP32.
13 This sample shows how to set a wake up source, trigger deep sleep and then
14 make use of that pre-configured wake up source to bring the system back again.
16 The following wake up sources are demonstrated in this example:
18 1. ``Timer``: An RTC timer that can be programmed to trigger a wake up after
19 a preset time. This example will trigger a wake up every 20 seconds.
20 2. ``EXT1``: External wake up 1 is tied to multiple RTC GPIOs. This example
21 uses GPIO2 and GPIO4 to trigger a wake up with any one of the two pins are
24 GPIOS0~5 can be used as wake-up sources.
26 In this demo, Timer is the only wake-up source that cannot be disabled via a
[all …]
DKconfig11 This option enables wake-up from deep sleep using GPIO2 and
13 avoid random wake-ups. Otherwise, external pull-down should
14 be used for the same purpose. To trigger a wake-up, connect
22 This option enables wake-up from GPIO. Only GPIO0~5 can be used
23 as wake-up source. Be aware that when low level is used to trigger
24 wake-up, an external pull-up resistance is necessary.
/Zephyr-latest/samples/kernel/condition_variables/simple/
DREADME.rst142 [thread zephyr_app_main] wake - cond was signalled.
145 [thread zephyr_app_main] wake - cond was signalled.
148 [thread zephyr_app_main] wake - cond was signalled.
151 [thread zephyr_app_main] wake - cond was signalled.
154 [thread zephyr_app_main] wake - cond was signalled.
157 [thread zephyr_app_main] wake - cond was signalled.
160 [thread zephyr_app_main] wake - cond was signalled.
163 [thread zephyr_app_main] wake - cond was signalled.
166 [thread zephyr_app_main] wake - cond was signalled.
169 [thread zephyr_app_main] wake - cond was signalled.
[all …]
/Zephyr-latest/samples/boards/st/power_mgmt/wkup_pins/
DREADME.rst2 :name: GPIO as a wake-up pin source
5 Use a GPIO as a wake-up pin source.
10 This sample is a minimum application to demonstrate using a wake-up pin with a GPIO as
21 The SoC should support POWEROFF functionality & have a wake-up pin that corresponds
24 Make sure that wake-up pins are configured in SoC dtsi file.
/Zephyr-latest/samples/boards/nordic/system_off/
DKconfig11 bool "Use button to wake up device from system off"
17 bool "Use GRTC to wake up device from system off"
22 bool "Use COMP to wake up device from system off"
/Zephyr-latest/tests/benchmarks/latency_measure/
DREADME.rst22 * Time it takes to wake and switch to a thread waiting on a fifo.LIFO
25 * Time it takes to wake and switch to a thread waiting for events
75 …fifo.put.wake+ctx.k_to_k - Add data to FIFO (w/ ctx switch) : …
77 …fifo.put.alloc.wake+ctx.k_to_k - Allocate to add data to FIFO (w/ ctx switch) : …
83 …lifo.put.wake+ctx.k_to_k - Add data to LIFO (w/ ctx switch) : …
85 …lifo.put.alloc.wake+ctx.k_to_k - Allocate to add data to LIFO (w/ ctx siwtch) : …
91 …events.set.wake+ctx.k_to_k - Set events (w/ ctx switch) : …
93 …events.post.wake+ctx.k_to_k - Post events (w/ ctx switch) : …
97 …semaphore.give.wake+ctx.k_to_k - Give a semaphore (context switch) : …
99 …condvar.signal.wake+ctx.k_to_k - Signal a condvar (context switch) : …
[all …]
/Zephyr-latest/samples/boards/nxp/mimxrt1060_evk/system_off/
DREADME.rst15 additionally set an alarm 10 seconds in the future to wake up the processor
39 to wake the device and restart the application as if it had been
41 alarm to fire and wake the device up automatically.
55 RTC Alarm set for 10 seconds to wake from soft-off.
/Zephyr-latest/include/zephyr/drivers/misc/
DREADME20 STM32 wake-up pins are part of the Power Control (PWR) peripheral.
21 They can be used to wake-up the system from Poweroff through GPIO pins.
/Zephyr-latest/include/zephyr/drivers/interrupt_controller/
Dnxp_pint.h55 int nxp_pint_pin_enable(uint8_t pin, enum nxp_pint_trigger trigger, bool wake);
/Zephyr-latest/samples/boards/espressif/deep_sleep/socs/
Desp32c3.overlay10 * as wake-up sources
/Zephyr-latest/drivers/timer/
DKconfig.gecko14 to be able to keep track of time and wake up from EM2 & EM3 sleep
26 work, k_sleep, will issue thread wake ups less precisely than when
/Zephyr-latest/doc/services/pm/
Dsystem.rst15 It is the application's responsibility to set up a wake-up event.
16 A wake-up event will typically be an interrupt triggered by an SoC peripheral module.
20 some wake-up sources may not be usable in all power modes.
40 … pm_system_resume [label="Finish wake-up\n(SoC API)\n(restore interruptions)" style="rounded,bold"]
79 (higher index in the enum) will offer greater power savings and have higher wake latencies.
/Zephyr-latest/samples/sensor/ccs811/boards/
Dnrf51_ble400.overlay35 wake-gpios = <&gpio0 5 GPIO_ACTIVE_LOW>;
/Zephyr-latest/dts/arm/nxp/
Dnxp_k66.dtsi31 "rx-warning", "wake-up";
/Zephyr-latest/drivers/counter/
DKconfig.mcux_snvs21 bool "IMX SNVS wake-up on SRTC alarm"
/Zephyr-latest/boards/shields/tcan4550evm/
Dtcan4550evm.overlay27 device-wake-gpios = <&arduino_header 13 GPIO_ACTIVE_HIGH>; /* D7 */
/Zephyr-latest/drivers/interrupt_controller/
Dintc_nxp_pint.c66 int nxp_pint_pin_enable(uint8_t pin, enum nxp_pint_trigger trigger, bool wake) in nxp_pint_pin_enable() argument
98 if (wake) { in nxp_pint_pin_enable()
/Zephyr-latest/boards/arm/mps2/
DCMakeLists.txt8 # for CPU0, which will boot the device and wake up CPU1.
/Zephyr-latest/drivers/sensor/st/lis2dw12/
DKconfig77 The wake-up interrupt signal is generated if a certain number of
80 a wake-up interrupt generation at least one of the three axes must
/Zephyr-latest/boards/silabs/dev_kits/sltb010a/
Dthunderboard.dtsi36 wake_up_trigger: gpio-wake-up {
37 compatible = "silabs,gecko-wake-up-trigger";
/Zephyr-latest/boards/silabs/dev_kits/xg27_dk2602a/
Dthunderboard.dtsi36 wake_up_trigger: gpio-wake-up {
37 compatible = "silabs,gecko-wake-up-trigger";
/Zephyr-latest/boards/sparkfun/thing_plus_matter_mgm240p/
Dsparkfun_thing_plus_matter_mgm240p.dts41 wake_up_trigger: gpio-wake-up {
42 compatible = "silabs,gecko-wake-up-trigger";
/Zephyr-latest/soc/native/inf_clock/
DKconfig.soc9 each wake reason (e.g. interrupts), before going back to idle. Note that an
/Zephyr-latest/boards/silabs/dev_kits/xg24_ek2703a/
Dxg24_ek2703a.dts57 wake_up_trigger: gpio-wake-up {
58 compatible = "silabs,gecko-wake-up-trigger";
/Zephyr-latest/drivers/spi/
DKconfig.nrfx108 int "Maximum time to wait for SPI slave to wake up"
112 for SPI slave to wake up after the WAKE line is asserted. Used only
113 by instances that have the WAKE line configured (see the wake-gpios

1234