| /Zephyr-Core-3.6.0/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
25 module-str = System Power Management
29 bool "System Power Management Stats"
32 Enable System Power Management Stats.
41 bool "System Low Power Mode Needs All Devices Idle"
45 entering into system low power mode.
[all …]
|
| /Zephyr-Core-3.6.0/doc/services/pm/ |
| D | system.rst | 3 System Power Management
7 the :kconfig:option:`CONFIG_PM` Kconfig option, the Power Management
8 Subsystem can put an idle system in one of the supported power states, based
9 on the selected power management policy and the duration of the idle time
14 such as a SysTick, RTC, counter, or GPIO. Depending on the power mode entered,
18 The following diagram describes system power management:
22 :alt: System power management
24 Some handful examples using different power management features:
33 Power States
36 The power management subsystem contains a set of states based on
[all …]
|
| 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 types of device power management:
15 - :ref:`Device Runtime Power Management <pm-device-runtime-pm>`
16 - :ref:`System Power Management <pm-device-system-pm>`
20 Device Runtime Power Management
24 and has the best knowledge of their use, performs the device power management. This
25 saves power if some devices that are not in use can be turned off or put
[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 …]
|
| D | overview.rst | 4 The interfaces and APIs provided by the power management subsystem
5 are designed to be architecture and SOC independent. This enables power
14 The power management features are classified into the following categories.
16 * System Power Management
17 * Device Power Management
|
| /Zephyr-Core-3.6.0/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-Core-3.6.0/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-Core-3.6.0/tests/subsys/pm/device_driver_init/ |
| D | app.overlay | 3 compatible = "power-domain-gpio";
8 compatible = "power-domain-gpio";
10 power-domain = <&test_reg>;
14 compatible = "power-domain-gpio";
16 power-domain = <&test_reg>;
21 compatible = "power-domain-gpio";
27 compatible = "power-domain-gpio";
29 power-domain = <&test_reg_auto>;
33 compatible = "power-domain-gpio";
35 power-domain = <&test_reg_auto>;
[all …]
|
| /Zephyr-Core-3.6.0/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 = "suspend-to-ram";
29 compatible = "zephyr,power-state";
30 power-state-name = "standby";
34 compatible = "zephyr,power-state";
35 power-state-name = "suspend-to-ram";
|
| /Zephyr-Core-3.6.0/include/zephyr/pm/ |
| D | pm.h | 22 * @brief System and device power management
23 * @defgroup subsys_pm Power Management (PM)
30 * @brief System Power Management API
37 * Power management notifier struct
40 * exits power states.
58 * for power state entry.
63 * for power state exit.
70 * @brief Force usage of given power state.
73 * usage of given power state upon next entry of the idle thread.
78 * @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 …]
|
| D | policy.h | 22 * @brief System Power Management Policy API
78 * This function is called by the power subsystem when the system is
85 * @return The power state the system should use for the given cpu. The function
97 * @brief Increase a power state lock counter.
99 * A power state will not be allowed on the first call of
108 * @param state Power state.
109 * @param substate_id Power substate ID. Use PM_ALL_SUBSTATES to affect all the
110 * substates in the given power state.
117 * @brief Decrease a power state lock counter.
119 * @param state Power state.
[all …]
|
| /Zephyr-Core-3.6.0/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
|
| 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
|
| /Zephyr-Core-3.6.0/soc/xtensa/intel_adsp/ace/include/intel_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
92 * @brief Retrieve node identifier for Intel ADSP HOST power domain.
[all …]
|
| /Zephyr-Core-3.6.0/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-Core-3.6.0/samples/boards/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-Core-3.6.0/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-Core-3.6.0/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-Core-3.6.0/soc/xtensa/intel_adsp/ace/include/intel_ace20_lnl/ |
| D | adsp_power.h | 29 /* Power control */
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
92 * @brief Retrieve node identifier for Intel ADSP HOST power domain.
97 * @brief Intel ADSP HOST power domain pointer.
|
| /Zephyr-Core-3.6.0/samples/bluetooth/hci_pwr_ctrl/ |
| D | README.rst | 3 Bluetooth: HCI Power Control
9 This sample application demonstrates the dynamic Tx power control over the LL
11 peripheral advertising with varying Tx power. The initial advertiser TX power
12 for the first 5s of the application is the Kconfig set default TX power. Then,
13 the TX power variation of the advertiser is a repeatedly descending staircase
14 pattern ranging from -4 dBm to -30 dBm where the Tx power levels decrease every
18 the Tx power of the peripheral device is modulated per connection accordingly
|
| /Zephyr-Core-3.6.0/drivers/pm_cpu_ops/ |
| D | Kconfig | 1 # CPU power management driver configuration options
7 bool "CPU power management drivers"
9 Enable CPU power management drivers configuration
21 bool "Support for the ARM Power State Coordination Interface (PSCI)"
28 implementing the PSCI specification for CPU-centric power
30 0022A ("Power State Coordination Interface System Software on
|
| /Zephyr-Core-3.6.0/dts/bindings/lora/ |
| D | st,stm32wl-subghz-radio.yaml | 16 power-amplifier-output:
20 Selects between the low- and high-power power amplifier output pin.
25 rfo-lp-max-power:
29 Maximum design power for the board's RFO_LP output matching network.
41 rfo-hp-max-power:
45 Maximum design power for the board's RFO_HP output matching network.
|
| /Zephyr-Core-3.6.0/dts/bindings/usb-c/ |
| D | usb-c-connector.yaml | 15 power delivery support and enables SINK.
32 power-role = "sink";
60 Power path controller for this port
62 power-role:
70 The Port power role. "dual" for Dual Role Port.
72 try-power-role:
79 Preferred power role.
93 typec-power-opmode:
100 Initial Type C advertised power, determined by the Rp when
112 Disables power delivery when true
[all …]
|
| /Zephyr-Core-3.6.0/doc/ |
| D | glossary.rst | 52 device runtime power management
53 Device Runtime Power Management (PM) refers the capability of devices to
54 save energy independently of the system power state. Devices will keep
78 power domain
79 A power domain is a collection of devices for which power is
80 applied and removed collectively in a single action. Power
83 power gating
84 Power gating reduces power consumption by shutting off areas of an
90 system power state
91 System power states describe the power consumption of the system as a
[all …]
|
