Lines Matching +full:pm +full:- +full:domains
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#
7 title: Generic PM domains
10 - Rafael J. Wysocki <[email protected]>
11 - Kevin Hilman <[email protected]>
12 - Ulf Hansson <[email protected]>
15 System on chip designs are often divided into multiple PM domains that can be
17 leakage current. Moreover, in some cases the similar PM domains may also be
20 This device tree binding can be used to bind PM domain consumer devices with
21 their PM domains provided by PM domain providers. A PM domain provider can be
22 represented by any node in the device tree and can provide one or more PM
23 domains. A consumer node can refer to the provider by a phandle and a set of
24 phandle arguments (so called PM domain specifiers) of length specified by the
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
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":
56 Number of cells in a PM domain specifier. Typically 0 for nodes
57 representing a single PM domain and 1 for nodes providing multiple PM
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
66 dependencies). For representing such dependency a standard PM domain
67 consumer binding is used. When provided, all domains created
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>;
102 // Domains created by the 'child' power controller are subdomains of '0' power
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>;