bindings/power/power-domain.yaml

1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/power-domain.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10   - Rafael J. Wysocki <rjw@rjwysocki.net>
11   - Kevin Hilman <khilman@kernel.org>
12   - Ulf Hansson <ulf.hansson@linaro.org>
16   used for power gating of selected IP blocks for power saving by reduced
25   \#power-domain-cells property in the PM domain provider node.
29     pattern: "^(power-controller|power-domain|performance-domain)([@-].*)?$"
31   domain-idle-states:
32     $ref: /schemas/types.yaml#/definitions/phandle-array
37       power-domain provider. The idle state definitions are compatible with the
38       domain-idle-state bindings, specified in ./domain-idle-state.yaml.
40       Note that, the domain-idle-state property reflects the idle states of this
41       PM domain and not the idle states of the devices or sub-domains in the PM
42       domain. Devices and sub-domains have their own idle states independent of
44       domain would be considered as capable of being powered-on or powered-off.
46   operating-points-v2:
48       Phandles to the OPP tables of power domains that are capable of scaling
49       performance, provided by a power domain provider. If the provider provides
50       a single power domain only or all the power domains provided by the
52       phandle. Refer to ../opp/opp-v2-base.yaml for more information.
54   "#power-domain-cells":
58       domains (e.g. power controllers), but can be any value as specified
61   power-domains:
63       A phandle and PM domain specifier as defined by bindings of the power
64       controller specified by phandle. Some power domains might be powered
65       from another power domain (or have other hardware specific
72   - "#power-domain-cells"
77   - |
78     power: power-controller@12340000 {
79         compatible = "foo,power-controller";
81         #power-domain-cells = <1>;
84     // The node above defines a power controller that is a PM domain provider and
87   - |
88     parent2: power-controller@12340000 {
89         compatible = "foo,power-controller";
91         #power-domain-cells = <1>;
94     child2: power-controller@12341000 {
95         compatible = "foo,power-controller";
97         power-domains = <&parent2 0>;
98         #power-domain-cells = <1>;
101     // The nodes above define two power controllers: 'parent' and 'child'.
102     // Domains created by the 'child' power controller are subdomains of '0' power
103     // domain provided by the 'parent' power controller.
105   - |
106     parent3: power-controller@12340000 {
107         compatible = "foo,power-controller";
109         #power-domain-cells = <0>;
110         domain-idle-states = <&DOMAIN_RET>, <&DOMAIN_PWR_DN>;
113     child3: power-controller@12341000 {
114         compatible = "foo,power-controller";
116         power-domains = <&parent3>;
117         #power-domain-cells = <0>;
118         domain-idle-states = <&DOMAIN_PWR_DN>;
121     domain-idle-states {
122         DOMAIN_RET: domain-retention {
123             compatible = "domain-idle-state";
124             entry-latency-us = <1000>;
125             exit-latency-us = <2000>;
126             min-residency-us = <10000>;
129         DOMAIN_PWR_DN: domain-pwr-dn {
130             compatible = "domain-idle-state";
131             entry-latency-us = <5000>;
132             exit-latency-us = <8000>;
133             min-residency-us = <7000>;