| /Zephyr-latest/subsys/pm/ |
| D | Kconfig | 5 menu "Power Management"
11 calls to configure low-power states.
14 bool "System Power Management"
17 This option enables the board to implement extra power management
19 power management subsystem of the number of ticks until the next kernel
27 module-str = System Power Management
31 bool "System Power Management Stats"
34 Enable System Power Management Stats.
50 bool "System Low Power Mode Needs All Devices Idle"
54 entering into system low power mode.
[all …]
|
| /Zephyr-latest/tests/subsys/pm/device_driver_init/ |
| D | app.overlay | 3 compatible = "power-domain-gpio";
5 #power-domain-cells = <0>;
9 compatible = "power-domain-gpio";
11 power-domains = <&test_reg>;
12 #power-domain-cells = <0>;
16 compatible = "power-domain-gpio";
18 power-domains = <&test_reg>;
19 #power-domain-cells = <0>;
24 compatible = "power-domain-gpio";
26 #power-domain-cells = <0>;
[all …]
|
| /Zephyr-latest/drivers/power_domain/ |
| D | Kconfig | 5 bool "Power domain drivers"
7 Include drivers for power domains in system config
16 int "Power domain init priority"
19 Power domain initialization priority.
22 bool "GPIO controlled power domain"
33 int "GPIO power domain init priority"
36 GPIO power domain initialization priority.
41 bool "Use Intel ADSP power gating mechanisms"
46 Include Intel ADSP power domain control mechanisms
51 int "Intel ADSP power domain init priority"
[all …]
|
| /Zephyr-latest/doc/services/pm/ |
| D | device.rst | 1 Device Power Management
7 Device power management (PM) on Zephyr is a feature that enables devices to
10 selected, device drivers implementing power management will be able to take
11 advantage of the device power management subsystem.
13 Zephyr supports two methods of device power management:
15 - :ref:`Device Runtime Power Management <pm-device-runtime-pm>`
16 - :ref:`System-Managed Device Power Management <pm-device-system-pm>`
20 Device Runtime Power Management
23 Device runtime power management involves coordinated interaction between
25 play a crucial role in directly controlling the power state of
[all …]
|
| D | system.rst | 3 System Power Management
11 power management subsystem to put an idle system into one of the supported power states.
13 the appropriate power state to transition to based on the configured power management policy.
18 Keep in mind that depending on the SoC and the power mode in question,
20 some wake-up sources may not be usable in all power modes.
22 The following diagram describes system power management:
25 :caption: System power management
36 pm_policy [label="Check policy manager\nfor a power state "]
39 pm_state_set [label="Change power state\n(SoC API)" style="rounded,bold"]
65 pm_policy -> k_cpu_idle [label="PM_STATE_ACTIVE\n(no power state meet requirements)"]
[all …]
|
| D | power_domain.rst | 1 .. _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
28 :caption: Power domain work flow
[all …]
|
| /Zephyr-latest/boards/renesas/rcar_h3ulcb/ |
| D | rcar_h3ulcb_r8a77951_a57-pinctrl.dtsi | 20 power-source = <PIN_VOLTAGE_3P3V>;
25 power-source = <PIN_VOLTAGE_3P3V>;
30 power-source = <PIN_VOLTAGE_3P3V>;
35 power-source = <PIN_VOLTAGE_3P3V>;
40 power-source = <PIN_VOLTAGE_3P3V>;
45 power-source = <PIN_VOLTAGE_3P3V>;
50 power-source = <PIN_VOLTAGE_1P8V>;
55 power-source = <PIN_VOLTAGE_1P8V>;
60 power-source = <PIN_VOLTAGE_1P8V>;
65 power-source = <PIN_VOLTAGE_1P8V>;
[all …]
|
| /Zephyr-latest/drivers/lora/ |
| D | sx126x_stm32wl.c | 53 void sx126x_set_tx_params(int8_t power, RadioRampTimes_t ramp_time) in sx126x_set_tx_params() argument
60 if (power > max_power) { in sx126x_set_tx_params()
61 power = max_power; in sx126x_set_tx_params()
65 power = 14 - (max_power - power); in sx126x_set_tx_params()
68 power = 13 - (max_power - power); in sx126x_set_tx_params()
71 power = 14 - (max_power - power); in sx126x_set_tx_params()
73 if (power < -17) { in sx126x_set_tx_params()
74 power = -17; in sx126x_set_tx_params()
80 /* Better Resistance of the RFO High Power Tx to Antenna in sx126x_set_tx_params()
89 if (power > max_power) { in sx126x_set_tx_params()
[all …]
|
| /Zephyr-latest/dts/bindings/power-domain/ |
| D | power-domain-gpio-monitor.yaml | 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
24 "#power-domain-cells":
|
| D | intel,adsp-power-domain.yaml | 5 description: Power domains for intel ADSP
7 compatible: "intel,adsp-power-domain"
9 include: power-domain.yaml
17 read_address (PWRSTS) to set power active or confirm power active
21 "#power-domain-cells":
|
| /Zephyr-latest/tests/subsys/pm/power_states_api/boards/ |
| D | native_sim.overlay | 10 cpu-power-states = <&state0 &state1 &state2 &state3>;
13 power-states {
15 compatible = "zephyr,power-state";
16 power-state-name = "suspend-to-idle";
22 compatible = "zephyr,power-state";
23 power-state-name = "standby";
29 compatible = "zephyr,power-state";
30 power-state-name = "suspend-to-ram";
36 compatible = "zephyr,power-state";
37 power-state-name = "suspend-to-disk";
[all …]
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | power_management.rst | 1 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
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
18 …ith :ref:`sensor-read-and-decode` its possible that automatic management of device power management
|
| /Zephyr-latest/include/zephyr/pm/ |
| D | pm.h | 22 * @brief System and device power management
23 * @defgroup subsys_pm Power Management (PM)
31 * @brief System Power Management API
39 * Power management notifier struct
42 * exits power states.
60 * for power state entry.
65 * for power state exit.
72 * @brief Force usage of given power state.
75 * usage of given power state upon next entry of the idle thread.
80 * @param info Power state which should be used in the ongoing
[all …]
|
| D | state.h | 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.
62 * In addition to putting peripherals into low-power states all
99 * This state consumes a minimal amount of power and requires a large
102 * restarted as if from initial power-up and kernel boot.
107 /** Number of power management states (internal use) */
112 * Information about a power management state
119 * one Zephyr power state. This property allows the platform
123 * power-states {
[all …]
|
| /Zephyr-latest/tests/subsys/pm/device_power_domains/ |
| D | app.overlay | 3 compatible = "power-domain-gpio";
5 #power-domain-cells = <0>;
9 compatible = "power-domain-gpio";
11 #power-domain-cells = <0>;
15 compatible = "power-domain-gpio";
17 power-domains = <&test_reg_0>;
18 #power-domain-cells = <0>;
24 power-domains = <&test_reg_1>;
|
| /Zephyr-latest/soc/intel/intel_adsp/ace/include/ace15_mtpm/ |
| D | adsp_power.h | 17 /* Power Control register - controls the power domain operations. */
34 /* Power Status register - reports the power domain status. */
50 * @brief Power up a specific CPU.
52 * This sets the "not power gating" bit in the power control
53 * register to disable power gating to CPU, thus powering up
64 * @brief Power down a specific CPU.
66 * This clears the "not power gating" bit in the power control
67 * register to enable power gating to CPU, thus powering down
80 * This queries the power status register to see if the CPU
98 * @brief Retrieve node identifier for Intel ADSP HOST power domain.
[all …]
|
| /Zephyr-latest/boards/renesas/rcar_salvator_xs/ |
| D | rcar_salvator_xs-pinctrl.dtsi | 20 power-source = <PIN_VOLTAGE_1P8V>;
25 power-source = <PIN_VOLTAGE_1P8V>;
30 power-source = <PIN_VOLTAGE_1P8V>;
35 power-source = <PIN_VOLTAGE_1P8V>;
40 power-source = <PIN_VOLTAGE_1P8V>;
45 power-source = <PIN_VOLTAGE_1P8V>;
50 power-source = <PIN_VOLTAGE_1P8V>;
55 power-source = <PIN_VOLTAGE_1P8V>;
60 power-source = <PIN_VOLTAGE_1P8V>;
65 power-source = <PIN_VOLTAGE_1P8V>;
|
| /Zephyr-latest/boards/renesas/rcar_spider_s4/ |
| D | rcar_spider_s4_r8a779f0_a55-pinctrl.dtsi | 20 power-source = <PIN_VOLTAGE_1P8V>;
25 power-source = <PIN_VOLTAGE_1P8V>;
30 power-source = <PIN_VOLTAGE_1P8V>;
35 power-source = <PIN_VOLTAGE_1P8V>;
40 power-source = <PIN_VOLTAGE_1P8V>;
45 power-source = <PIN_VOLTAGE_1P8V>;
50 power-source = <PIN_VOLTAGE_1P8V>;
55 power-source = <PIN_VOLTAGE_1P8V>;
60 power-source = <PIN_VOLTAGE_1P8V>;
65 power-source = <PIN_VOLTAGE_1P8V>;
|
| /Zephyr-latest/samples/boards/microchip/mec172xevb_assy6906/qmspi_ldma/ |
| D | mec172xevb_assy6906.overlay | 13 low-power-enable;
17 low-power-enable;
21 low-power-enable;
25 low-power-enable;
29 low-power-enable;
33 low-power-enable;
38 low-power-enable;
42 low-power-enable;
46 low-power-enable;
50 low-power-enable;
[all …]
|
| /Zephyr-latest/samples/subsys/pm/latency/boards/ |
| D | native_sim.overlay | 7 power-states {
9 compatible = "zephyr,power-state";
10 power-state-name = "runtime-idle";
15 compatible = "zephyr,power-state";
16 power-state-name = "suspend-to-idle";
21 compatible = "zephyr,power-state";
22 power-state-name = "standby";
30 cpu-power-states = <&runtime_idle &suspend_to_idle &standby>;
|
| /Zephyr-latest/tests/subsys/pm/policy_api/ |
| D | app.overlay | 11 cpu-power-states = <&state2>;
15 power-states {
17 compatible = "zephyr,power-state";
18 power-state-name = "runtime-idle";
25 compatible = "zephyr,power-state";
26 power-state-name = "suspend-to-ram";
33 compatible = "zephyr,power-state";
34 power-state-name = "suspend-to-ram";
43 cpu-power-states = <&state0 &state1>;
|
| /Zephyr-latest/soc/intel/intel_adsp/ace/include/ace30/ |
| D | adsp_power.h | 17 /* Power Control register - controls the power domain operations. */
38 /* Power Status register - reports the power domain status. */
60 * @brief Power up a specific CPU.
62 * This sets the "not power gating" bit in the power control
63 * register to disable power gating to CPU, thus powering up
74 * @brief Power down a specific CPU.
76 * This clears the "not power gating" bit in the power control
77 * register to enable power gating to CPU, thus powering down
90 * This queries the power status register to see if the CPU
109 * @brief Retrieve node identifier for Intel ADSP HOST power domain.
[all …]
|
| /Zephyr-latest/dts/bindings/mtd/ |
| D | jedec,spi-nor-common.yaml | 33 Power-Down mode that is entered by command 0xB9 to reduce power
35 implies that the RDPD (0xAB) Release from Deep Power Down command
44 Some devices (Macronix MX25R in particular) wake from deep power
48 (1) tDPDD (Delay Time for Release from Deep Power-Down Mode)
49 (2) tCDRP (CSn Toggling Time before Release from Deep Power-Down Mode)
50 (3) tRDP (Recovery Time for Release from Deep Power-Down Mode)
53 used to wake the chip from Deep Power-Down mode.
62 deep power down.
73 deep power down and be ready to receive additional commands.
83 Some devices from certain vendors power-up with block protect bits
[all …]
|
| /Zephyr-latest/tests/subsys/pm/power_domain/ |
| D | app.overlay | 9 compatible = "power-domain";
11 #power-domain-cells = <0>;
17 power-domains = <&test_domain>;
23 power-domains = <&test_domain>;
27 compatible = "power-domain";
29 #power-domain-cells = <0>;
35 power-domains = <&test_domain_balanced>;
|
| /Zephyr-latest/samples/bluetooth/hci_pwr_ctrl/ |
| D | README.rst | 2 :name: HCI Power Control
5 Dynamically control the Tx power of a Bluetooth LE Controller using HCI vendor-specific commands.
10 This sample application demonstrates the dynamic Tx power control over the LL
12 peripheral advertising with varying Tx power. The initial advertiser TX power
13 for the first 5s of the application is the Kconfig set default TX power. Then,
14 the TX power variation of the advertiser is a repeatedly descending staircase
15 pattern ranging from -4 dBm to -30 dBm where the Tx power levels decrease every
19 the Tx power of the peripheral device is modulated per connection accordingly
|
