Lines Matching full:power

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
49 Internal Power Domains
52 Most of the devices in an SoC have independent power control that can
53 be turned on or off to reduce power consumption. But there is a
55 only using device power management. To solve this problem, SoCs
59 called "power domains", can be present in a hierarchy and can be
62 External Power Domains
65 Devices external to a SoC can be powered from sources other than the main power
67 or a dedicated power IC. Multiple devices can be powered from the same source,
68 and this grouping of devices is typically called a "power domain".
70 Placing devices on power domains can be done for a variety of reasons,
71 including to enable devices with high power consumption in low power mode to be
77 In a first place, a device that acts as a power domain needs to
78 declare compatible with ``power-domain``. Taking
85 		compatible = "power-domain";
89 A power domain needs to implement the PM action callback used by the
126 ``power-domain`` node's property. The example below declares devices
134                 power-domains = <&gpio_domain>;
140                 power-domains = <&gpio_domain>;
163             /* configure the device into low power mode */
167             /* prepare the device for power down */
185 Some helpful examples showing power domain features: