Lines Matching +full:domain +full:- +full:idle +full:- +full:states
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>
19 This device tree binding can be used to bind PM domain consumer devices with
20 their PM domains provided by PM domain providers. A PM domain provider can be
23 phandle arguments (so called PM domain specifiers) of length specified by the
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
35 Phandles of idle states that defines the available states for the
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
42 the parent domain's idle states. In the absence of this property, the
43 domain would be considered as capable of being powered-on or powered-off.
45 operating-points-v2:
46 $ref: /schemas/types.yaml#/definitions/phandle-array
50 Phandles to the OPP tables of power domains provided by a power domain
51 provider. If the provider provides a single power domain only or all
53 then this shall contain a single phandle. Refer to ../opp/opp-v2-base.yaml
56 "#power-domain-cells":
58 Number of cells in a PM domain specifier. Typically 0 for nodes
59 representing a single PM domain and 1 for nodes providing multiple PM
63 power-domains:
65 A phandle and PM domain specifier as defined by bindings of the power
67 from another power domain (or have other hardware specific
68 dependencies). For representing such dependency a standard PM domain
70 by the given provider should be subdomains of the domain specified
74 - "#power-domain-cells"
79 - |
80 power: power-controller@12340000 {
81 compatible = "foo,power-controller";
83 #power-domain-cells = <1>;
86 // The node above defines a power controller that is a PM domain provider and
89 - |
90 parent2: power-controller@12340000 {
91 compatible = "foo,power-controller";
93 #power-domain-cells = <1>;
96 child2: power-controller@12341000 {
97 compatible = "foo,power-controller";
99 power-domains = <&parent2 0>;
100 #power-domain-cells = <1>;
105 // domain provided by the 'parent' power controller.
107 - |
108 parent3: power-controller@12340000 {
109 compatible = "foo,power-controller";
111 #power-domain-cells = <0>;
112 domain-idle-states = <&DOMAIN_RET>, <&DOMAIN_PWR_DN>;
115 child3: power-controller@12341000 {
116 compatible = "foo,power-controller";
118 power-domains = <&parent3>;
119 #power-domain-cells = <0>;
120 domain-idle-states = <&DOMAIN_PWR_DN>;
123 domain-idle-states {
124 DOMAIN_RET: domain-retention {
125 compatible = "domain-idle-state";
126 entry-latency-us = <1000>;
127 exit-latency-us = <2000>;
128 min-residency-us = <10000>;
131 DOMAIN_PWR_DN: domain-pwr-dn {
132 compatible = "domain-idle-state";
133 entry-latency-us = <5000>;
134 exit-latency-us = <8000>;
135 min-residency-us = <7000>;