Home
last modified time | relevance | path

Searched +full:power +full:- +full:off (Results 1 – 25 of 412) sorted by relevance

12345678910>>...17

/Zephyr-latest/include/zephyr/sys/
Dpoweroff.h4 * SPDX-License-Identifier: Apache-2.0
17 * @defgroup sys_poweroff System power off
25 * @brief System power off hook.
28 * perform an immediate power off of the system.
35 * @brief Perform a system power off.
37 * This function will perform an immediate power off of the system. It is the
39 * be powered off. Any required wake up sources must be enabled before calling
/Zephyr-latest/doc/services/pm/
Dpower_domain.rst1 .. _pm-power-domain:
3 Power Domain
9 The Zephyr power domain abstraction is designed to support groupings of devices
10 powered by a common source to be notified of power source state changes in a
12 that device B is on the same power domain and should also be configured into a
13 low power state.
15 Power domains are optional on Zephyr, to enable this feature the
18 When a power domain turns itself on or off, it is the responsibility of the
19 power domain to notify all devices using it through their power management
25 .. _pm-domain-work-flow:
[all …]
/Zephyr-latest/samples/boards/nxp/mimxrt1060_evk/system_off/
DREADME.rst1 .. zephyr:code-sample:: mimxrt1060_evk_system_off
2 :name: RT1060 System Off
3 :relevant-api: sys_poweroff
5 Use soft-off on MIMXRT1060-EVK.
10 This sample can be used for basic power measurement and as an example of
11 soft off on NXP i.MX RT platforms. The functional behavior is:
13 * Busy-wait for 2 seconds
14 * Turn the system off after enabling wakeup through a button press, and
17 A power monitor will be able to distinguish among these states.
27 .. zephyr-app-commands::
[all …]
/Zephyr-latest/doc/services/resource_management/
Dindex.rst7 use at runtime among multiple clients. These include power rails,
8 clocks, other peripherals, and binary device power management. The
23 On-Off Manager
26 An on-off manager supports an arbitrary number of clients of a service
27 which has a binary state. Example applications are power rails, clocks,
28 and binary device power management.
32 * The stable states are off, on, and error. The service always begins
33 in the off state. The service may also be in a transition to a given
37 state) and cancel (to reclaim client data from an in-progress
40 * The service transitions from off to on when first client request is
[all …]
/Zephyr-latest/samples/boards/ti/cc13x2_cc26x2/system_off/
DREADME.rst1 .. zephyr:code-sample:: ti_cc13x2_cc26x2_system_off
2 :name: CC13x2/CC26x2 System Off
9 This sample can be used for basic power measurement and as an example of
13 * Busy-wait for 5 seconds
16 * Turn the system off after enabling wakeup through a button press
19 A power monitor (e.g. `EnergyTrace <http://www.ti.com/tool/ENERGYTRACE>`_)
30 .. zephyr-app-commands::
31 :zephyr-app: samples/boards/ti/cc13x2_cc26x2/system_off
39 power-cycle it.
42 4. Device will turn off the external flash, which is on by default, to
[all …]
/Zephyr-latest/samples/boards/st/power_mgmt/standby_shutdown/
Dsample.yaml2 name: STM32 GPIO Power Management
6 - nucleo_l476rg
7 - disco_l475_iot1
9 - LED
10 - power
15 - "Reset cause: Reset pin"
16 - "Device ready: .*"
17 - "Press and hold the user button:"
18 - "when LED2 is OFF to power off"
19 - "when LED2 is ON to enter to Standby Mode"
[all …]
/Zephyr-latest/soc/nordic/nrf54h/
Dpower.h3 * SPDX-License-Identifier: Apache-2.0
7 * @file Common power.h include for Nordic SoCs.
14 * @brief Perform a power off.
16 * This function performs a power off of the core.
/Zephyr-latest/samples/boards/nordic/system_off/
DREADME.rst1 .. zephyr:code-sample:: nrf_system_off
2 :name: System Off
3 :relevant-api: sys_poweroff subsys_pm_device
10 This sample can be used for basic power measurement and as an example of
18 number of times system off was entered, and total uptime since initial power-on
20 RAM is configured to keep the containing section powered while in system-off mode.
31 -----------------
33 .. code-block:: console
35 *** Booting Zephyr OS build v2.3.0-rc1-204-g5f2eb85f728d ***
37 nrf52dk system off demo
[all …]
Dsample.yaml2 name: Low Power State Sample for nRF5x
4 tags: power
8 - nrf52840dk/nrf52840
10 - nrf51dk/nrf51822
11 - nrf52840dk/nrf52840
12 - nrf52dk/nrf52832
13 - nrf5340dk/nrf5340/cpuapp
14 - nrf54l15dk/nrf54l05/cpuapp
15 - nrf54l15dk/nrf54l10/cpuapp
16 - nrf54l15dk/nrf54l15/cpuapp
[all …]
/Zephyr-latest/dts/bindings/power-domain/
Dpower-domain-gpio.yaml2 # SPDX-License-Identifier: Apache-2.0
4 description: Simple GPIO controlled power domain
6 compatible: "power-domain-gpio"
8 include: power-domain.yaml
11 enable-gpios:
12 type: phandle-array
18 provide the GPIO polarity and open-drain status in the phandle
19 selector. The Linux enable-active-high and gpio-open-drain
22 startup-delay-us:
27 off-on-delay-us:
[all …]
Dpower-domain-gpio-monitor.yaml2 # SPDX-License-Identifier: Apache-2.0
5 Simple monitorig power domain
7 This power domain monitors the state of a GPIO pin to detect whether a power
8 rail is on/off. Therefore, performing resume/suspend on power domain won't
9 change physical state of power rails and that action won't be triggered on
11 pending transaction won't be interrupted by power state change.
13 compatible: "power-domain-gpio-monitor"
15 include: power-domain.yaml
19 type: phandle-array
24 "#power-domain-cells":
/Zephyr-latest/samples/boards/st/power_mgmt/wkup_pins/
DREADME.rst1 .. zephyr:code-sample:: stm32_pm_gpio_wkup_src
2 :name: GPIO as a wake-up pin source
3 :relevant-api: sys_poweroff gpio_interface
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
11 a source to power on an STM32 SoC after Poweroff.
13 The system will power off automatically ``WAIT_TIME_US`` us after boot.
14 Press the user button designated in boards's devicetree overlay as "wkup-src" to power it on again.
16 .. _gpio-as-a-wkup-pin-src-sample-requirements:
21 The SoC should support POWEROFF functionality & have a wake-up pin that corresponds
[all …]
/Zephyr-latest/include/zephyr/dt-bindings/gpio/
Dnordic-npm1300-gpio.h4 * SPDX-License-Identifier: Apache-2.0
10 * @brief nPM1300-specific GPIO Flags
11 * @defgroup gpio_interface_npm1300 nPM1300-specific GPIO Flags
16 * - Bit 8: Drive strength (0=1mA, 1=6mA)
17 * - Bit 9: Debounce (0=OFF, 1=ON)
18 * - Bit 10: Watchdog reset (0=OFF, 1=ON)
19 * - Bit 11: Power loss warning (0=OFF, 1=ON)
72 /** Off */
80 * @name nPM1300 GPIO power loss warning flags
81 * @brief nPM1300 GPIO power loss warning flags
[all …]
/Zephyr-latest/soc/nuvoton/npcx/common/
Dpower.c4 * SPDX-License-Identifier: Apache-2.0
9 * @brief Nuvoton NPCX power management driver
11 * This file contains the drivers of NPCX Power Manager Modules that improves
12 * the efficiency of ec operation by adjusting the chip’s power consumption to
14 * summarizes the main properties of the various power states and shows the
15 * activity levels of the various clocks while in these power states.
17 * +--------------------------------------------------------------------------+
18 * | Power State | LFCLK | HFCLK | APB/AHB | Core | RAM/Regs | VCC | VSBY |
19 * |--------------------------------------------------------------------------|
23 * | Deep Sleep | On | Stop | Stop | Stop | Power Down | On | On |
[all …]
/Zephyr-latest/samples/boards/nxp/mimxrt595_evk/system_off/
DREADME.rst1 .. zephyr:code-sample:: mimxrt595_evk_system_off
2 :name: RT595 System Off
3 :relevant-api: sys_poweroff
5 Use soft-off on MIMXRT595-EVK.
10 This sample can be used for basic power measurement and as an example of
11 soft off on NXP i.MX RT platforms. The functional behavior is:
13 * Busy-wait for 2 seconds
14 * Turn the system off after enabling wakeup through RTC and set alarm
20 This application uses MIMXRT595-EVK for the demo.
25 .. zephyr-app-commands::
[all …]
/Zephyr-latest/dts/bindings/power/
Dst,stm32wb0-pwr.yaml2 # SPDX-License-Identifier: Apache-2.0
4 description: STM32WB0 power controller
6 compatible: "st,stm32wb0-pwr"
8 include: "st,stm32-pwr.yaml"
11 smps-mode:
17 OFF:
18 - SMPS converter disabled
19 - LDOs supply voltage: VDD
29 - SMPS converter enabled - clock disabled
30 - LDOs supply voltage: VDD (though SMPS)
[all …]
Dnuvoton,npcx-power-psl.yaml2 # SPDX-License-Identifier: Apache-2.0
4 description: Nuvoton, NPCX Power Switch Logic (PSL) control node
6 compatible: "nuvoton,npcx-power-psl"
8 include: [base.yaml, pinctrl-device.yaml]
11 enable-gpios:
12 type: phandle-array
15 GPIO to used to turn on/off the Core Domain power supply (VCC1) of NPCX
17 pinctrl-0:
19 pinctrl-names:
Dzephyr,power-state.yaml2 # SPDX-License-Identifier: Apache-2.0
4 description: Properties for power management state
6 compatible: "zephyr,power-state"
9 power-state-name:
12 description: indicates a power state
14 - "active"
15 - "runtime-idle"
16 - "suspend-to-idle"
17 - "standby"
18 - "suspend-to-ram"
[all …]
/Zephyr-latest/lib/utils/
DKconfig2 # SPDX-License-Identifier: Apache-2.0
17 For optimal performance, use buffer sizes that are a power of 2.
30 bool "On-Off Manager"
33 An on-off manager supports an arbitrary number of clients of a
34 service which has a binary state. Example applications are power
35 rails, clocks, and binary device power management.
41 "windows", generally for transmit to non-Zephyr contexts that
55 bool "UTF-8 string operation supported"
58 handle UTF-8 encoded strings.
/Zephyr-latest/dts/bindings/gnss/
Dluatos,air530z.yaml2 # SPDX-License-Identifier: Apache-2.0
9 - uart-device.yaml
12 on-off-gpios:
13 type: phandle-array
15 Identifies the On-Off pin for entering into low-power mode.
/Zephyr-latest/include/zephyr/arch/common/
Dpm_s2ram.h26 * @brief System off function
29 * to power the system off after the CPU context has been saved.
31 * This function never returns if the system is powered off. If the operation
35 * @retval none The system is powered off.
36 * @retval -EBUSY The system is busy and cannot be powered off at this time.
37 * @retval -errno Other error codes.
44 * This function is used on suspend-to-RAM (S2RAM) to save the CPU context in
45 * (retained) RAM before powering the system off using the provided function.
52 * @param system_off Function to power off the system.
55 * @retval -EBUSY The system is busy and cannot be suspended at this time.
[all …]
/Zephyr-latest/include/zephyr/pm/
Dstate.h4 * SPDX-License-Identifier: Apache-2.0
18 * @brief System Power Management States
25 * @enum pm_state Power management state
52 * peripherals into low-power states. No operating state is lost (ie.
54 * back to where it left off easily enough.
62 * In addition to putting peripherals into low-power states all
63 * non-boot CPUs are powered off. It should allow more energy to be
74 * This state offers significant energy savings by powering off as much
76 * self-refresh mode to retain its contents. The state of devices and
77 * CPUs is saved and held in memory, and it may require some boot-
[all …]
/Zephyr-latest/samples/basic/custom_dts_binding/dts/bindings/
Dpower-switch.yaml2 # SPDX-License-Identifier: Apache-2.0
4 description: GPIO pin to switch a power output on or off
6 compatible: "power-switch"
10 type: phandle-array
/Zephyr-latest/dts/bindings/sensor/
Dst,stts22h-i2c.yaml2 # SPDX-License-Identifier: Apache-2.0
6 When setting the sampling-rate property in a .dts or .dtsi file you
10 #include <zephyr/dt-bindings/sensor/stts22h.h>
15 sampling-rate = <STTS22H_100Hz>;
20 include: [sensor-device.yaml, i2c-device.yaml]
23 int-gpios:
24 type: phandle-array
31 temperature-hi-threshold:
36 Valid range is 0 to 255. It defaults to 0 (alarm off) which is
37 the configuration at power-up. This threshold must be calculated
[all …]
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dpower_management.rst1 Power Management
4 Power management of sensors is often a non-trivial task as sensors may have multiple power states
5 for various channels. Some sensors may allow for low noise, low power, or suspending channels
6 potentially saving quite a bit of power at the cost of noise or sampling speed performance. In very
7 low power states sensors may lose their state, turning off even the digital logic portion of the de…
9 All this is to say that power management of sensors is typically application specific! Often the
10 channel states are mutable using :ref:`sensor-attribute`. While total device suspending and resume
11 can be done using the power management ref counting APIs if the device implements the necessary
14 Most likely the API sensors should use for their fully suspended/resume power states is
15 :ref:`pm-device-runtime` using explicit calls at an application level to :c:func:`pm_device_runtime…
[all …]

12345678910>>...17