Home
last modified time | relevance | path

Searched refs:sleep (Results 451 – 475 of 500) sorted by relevance

1...<<11121314151617181920

/Zephyr-latest/boards/vcc-gnd/yd_esp32/doc/
Dindex.rst45 - 5uA deep sleep current
/Zephyr-latest/dts/arm/nxp/
Dnxp_rw6xx_common.dtsi55 deep-sleep-config = <0x180000>,
/Zephyr-latest/soc/espressif/esp32s3/
Ddefault.ld77 /* RTC fast memory (executable). Persists over deep sleep.
85 /* RTC slow memory (data accessible). Persists over deep sleep.
202 * and will be retained during deep sleep.
/Zephyr-latest/doc/kernel/services/timing/
Dtimers.rst213 If the thread had no other work to do it could simply sleep
/Zephyr-latest/boards/u-blox/ubx_bmd340eval/doc/
Dindex.rst487 pinctrl-names = "default", "sleep";
/Zephyr-latest/boards/u-blox/ubx_bmd345eval/doc/
Dindex.rst499 pinctrl-names = "default", "sleep";
/Zephyr-latest/boards/u-blox/ubx_bmd380eval/doc/
Dindex.rst484 pinctrl-names = "default", "sleep";
/Zephyr-latest/dts/arm/st/wba/
Dstm32wba.dtsi501 pinctrl-names = "default", "sleep";
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-ctlr-arch.rst315 - * A Low Frequency Clock (LFCLOCK) or sleep clock, for low power
/Zephyr-latest/soc/espressif/esp32c6/
Ddefault.ld196 * and will be retained during deep sleep.
224 * The data are not initialized at power-up and are retained during deep sleep.
/Zephyr-latest/boards/native/doc/
Darch_soc.rst103 something to happen without letting the CPU sleep.
483 after the simulated CPU goes to sleep for the first time,
/Zephyr-latest/drivers/wifi/nrf_wifi/
DKconfig.nrfwifi683 int "Minimum idle time to enter sleep in milliseconds"
688 sleep mode, assuming there is no activity.
/Zephyr-latest/samples/net/mqtt_publisher/
DREADME.rst49 Application sleep time:
/Zephyr-latest/soc/espressif/esp32s2/
Ddefault.ld234 * and will be retained during deep sleep.
262 * The data are not initialized at power-up and are retained during deep sleep.
/Zephyr-latest/tests/net/lib/lwm2m/interop/pytest/
Dtest_lwm2m.py54 time.sleep(1)
/Zephyr-latest/drivers/wifi/esp32/
DKconfig.esp32326 … before entering the sleep process. If a broadcast packet is received with more data bits, the time
/Zephyr-latest/tests/lib/devicetree/api/
Dapp.overlay415 pinctrl-names = "default", "sleep", "f.o.o2";
/Zephyr-latest/doc/hardware/porting/
Darch.rst42 for putting the CPU to sleep (partly optional, most likely very desired).
429 :code:`hlt` on x86, :code:`wfi` or :code:`wfe` on ARM, :code:`sleep` on ARC.
431 get interrupted or not by an interrupt before going to sleep. There are
/Zephyr-latest/doc/kernel/services/
Dinterrupts.rst137 then performs an operation that puts itself to sleep (e.g. sleeping
152 If thread A does not sleep but does make a higher-priority thread B
/Zephyr-latest/doc/services/portability/posix/option_groups/
Dindex.rst332 sleep(),yes
/Zephyr-latest/doc/releases/
Drelease-notes-1.6.rst365 * ``ZEP-1349`` - ARC sleep needs to pass interrupt priority threshold when interrupts are enabled
Drelease-notes-3.0.rst792 longer suspend and resume devices when the system goes to sleep
985 * :github:`41839` - BLE causes system sleep before main
1073 * :github:`41026` - LoRa: sx126x: DIO1 interrupt left enabled in sleep mode
/Zephyr-latest/doc/build/dts/
Dmacros.bnf127 ; pinctrl-names = "default", "sleep";
/Zephyr-latest/dts/arm/st/u5/
Dstm32u5.dtsi943 pinctrl-names = "default", "sleep";
/Zephyr-latest/boards/espressif/esp_wrover_kit/doc/
Dindex.rst74 | | low-power consumption while the chip is in Deep-sleep mode. |

1...<<11121314151617181920