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 leakage
24   \#power-domain-cells property in the PM domain provider node.
28     pattern: "^(power-controller|power-domain)([@-].*)?$"
30   domain-idle-states:
31     $ref: /schemas/types.yaml#/definitions/phandle-array
36       power-domain provider. The idle state definitions are compatible with the
37       domain-idle-state bindings, specified in ./domain-idle-state.yaml.
39       Note that, the domain-idle-state property reflects the idle states of this
40       PM domain and not the idle states of the devices or sub-domains in the PM
41       domain. Devices and sub-domains have their own idle states independent of
43       domain would be considered as capable of being powered-on or powered-off.
45   operating-points-v2:
47       Phandles to the OPP tables of power domains provided by a power domain
48       provider. If the provider provides a single power domain only or all
49       the power domains provided by the provider have identical OPP tables,
50       then this shall contain a single phandle. Refer to ../opp/opp-v2-base.yaml
53   "#power-domain-cells":
57       domains (e.g. power controllers), but can be any value as specified
60   power-domains:
62       A phandle and PM domain specifier as defined by bindings of the power
63       controller specified by phandle. Some power domains might be powered
64       from another power domain (or have other hardware specific
71   - "#power-domain-cells"
76   - |
77     power: power-controller@12340000 {
78         compatible = "foo,power-controller";
80         #power-domain-cells = <1>;
83     // The node above defines a power controller that is a PM domain provider and
86   - |
87     parent2: power-controller@12340000 {
88         compatible = "foo,power-controller";
90         #power-domain-cells = <1>;
93     child2: power-controller@12341000 {
94         compatible = "foo,power-controller";
96         power-domains = <&parent2 0>;
97         #power-domain-cells = <1>;
100     // The nodes above define two power controllers: 'parent' and 'child'.
101     // Domains created by the 'child' power controller are subdomains of '0' power
102     // domain provided by the 'parent' power controller.
104   - |
105     parent3: power-controller@12340000 {
106         compatible = "foo,power-controller";
108         #power-domain-cells = <0>;
109         domain-idle-states = <&DOMAIN_RET>, <&DOMAIN_PWR_DN>;
112     child3: power-controller@12341000 {
113         compatible = "foo,power-controller";
115         power-domains = <&parent3>;
116         #power-domain-cells = <0>;
117         domain-idle-states = <&DOMAIN_PWR_DN>;
120     domain-idle-states {
121         DOMAIN_RET: domain-retention {
122             compatible = "domain-idle-state";
123             entry-latency-us = <1000>;
124             exit-latency-us = <2000>;
125             min-residency-us = <10000>;
128         DOMAIN_PWR_DN: domain-pwr-dn {
129             compatible = "domain-idle-state";
130             entry-latency-us = <5000>;
131             exit-latency-us = <8000>;
132             min-residency-us = <7000>;