Lines Matching +full:on +full:- +full:off

1 .. _pm-power-domain:
12 that device B is on the same power domain and should also be configured into a
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
25 .. _pm-domain-work-flow:
42       action -> devA [label="pm_device_get()"]
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)"]
50 ----------------------
53 be turned on or off to reduce power consumption. But there is a
58 completely powered off to eliminate this leakage. These regions are
63 ----------------------
70 Placing devices on power domains can be done for a variety of reasons,
72 completely turned off when not in use.
78 declare compatible with ``power-domain``. Taking
79 :ref:`pm-domain-work-flow` as example, the following code defines a
82 .. code-block:: devicetree
85 		compatible = "power-domain";
90 PM subsystem to turn devices on and off.
92 .. code-block:: c
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) */
119             return -ENOTSUP;
126 ``power-domain`` node's property. The example below declares devices
129 .. code-block:: devicetree
132                 compatible = "zephyr,gpio-emul";
133                 gpio-controller;
134                 power-domains = <&gpio_domain>;
138                 compatible = "zephyr,gpio-emul";
139                 gpio-controller;
140                 power-domains = <&gpio_domain>;
148 .. code-block:: c
171             return -ENOTSUP;
180    "wakeup" source if a device depending on it is used as "wakeup" source.