Lines Matching full:domain

1 .. _pm-power-domain:
3 Power Domain
9 The Zephyr power domain abstraction is designed to support groupings of devices
12 that device B is on the same power domain and should also be configured into a
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:
28    :caption: Power domain work flow
40        domain [label="gpio_domain"]
43       devA:se -> domain:n [label="pm_device_get()"]
45       domain -> devB [label="action_cb(PM_DEVICE_ACTION_TURN_ON)"]
46       domain:sw -> devA:sw [label="action_cb(PM_DEVICE_ACTION_TURN_ON)"]
68 and this grouping of devices is typically called a "power domain".
77 In a first place, a device that acts as a power domain needs to
78 declare compatible with ``power-domain``. Taking
79 :ref:`pm-domain-work-flow` as example, the following code defines a
80 domain called ``gpio_domain``.
85 		compatible = "power-domain";
89 A power domain needs to implement the PM action callback used by the
99             /* resume the domain */
101             /* notify children domain is now powered */
105             /* notify children domain is going down */
107             /* suspend the domain */
111             /* turn on the domain (e.g. setup control pins to disabled) */
115             /* turn off the domain (e.g. reset control pins to default state) */
126 ``power-domain`` node's property. The example below declares devices
127 ``gpio0`` and ``gpio1`` belonging to domain ``gpio_domain```.
143 All devices under a domain will be notified when the domain changes
179    It is responsibility of driver or the application to set the domain as
185 Some helpful examples showing power domain features: