bindings/power/power_domain.txt

4 used for power gating of selected IP blocks for power saving by reduced leakage
7 This device tree binding can be used to bind PM domain consumer devices with
8 their PM domains provided by PM domain providers. A PM domain provider can be
11 phandle arguments (so called PM domain specifiers) of length specified by the
12 #power-domain-cells property in the PM domain provider node.
14 ==PM domain providers==
16 See power-domain.yaml.
18 ==PM domain consumers==
21  - power-domains : A list of PM domain specifiers, as defined by bindings of
22 		the power controller that is the PM domain provider.
25  - power-domain-names : A list of power domain name strings sorted in the same
26 		order as the power-domains property. Consumers drivers will use
27 		power-domain-names to match power domains with power-domains
32 	leaky-device@12350000 {
33 		compatible = "foo,i-leak-current";
35 		power-domains = <&power 0>;
36 		power-domain-names = "io";
39 	leaky-device@12351000 {
40 		compatible = "foo,i-leak-current";
42 		power-domains = <&power 0>, <&power 1> ;
43 		power-domain-names = "io", "clk";
46 The first example above defines a typical PM domain consumer device, which is
47 located inside a PM domain with index 0 of a power controller represented by a
48 node with the label "power".
50 the first with index 0 and the second with index 1, of a power controller that
51 is represented by a node with the label "power".
54 - required-opps: This contains phandle to an OPP node in another device's OPP
63 - OPP table for domain provider that provides two domains.
65 	domain0_opp_table: opp-table0 {
66 		compatible = "operating-points-v2";
68 		domain0_opp_0: opp-1000000000 {
69 			opp-hz = /bits/ 64 <1000000000>;
70 			opp-microvolt = <975000 970000 985000>;
72 		domain0_opp_1: opp-1100000000 {
73 			opp-hz = /bits/ 64 <1100000000>;
74 			opp-microvolt = <1000000 980000 1010000>;
78 	domain1_opp_table: opp-table1 {
79 		compatible = "operating-points-v2";
81 		domain1_opp_0: opp-1200000000 {
82 			opp-hz = /bits/ 64 <1200000000>;
83 			opp-microvolt = <975000 970000 985000>;
85 		domain1_opp_1: opp-1300000000 {
86 			opp-hz = /bits/ 64 <1300000000>;
87 			opp-microvolt = <1000000 980000 1010000>;
91 	power: power-controller@12340000 {
92 		compatible = "foo,power-controller";
94 		#power-domain-cells = <1>;
95 		operating-points-v2 = <&domain0_opp_table>, <&domain1_opp_table>;
98 	leaky-device0@12350000 {
99 		compatible = "foo,i-leak-current";
101 		power-domains = <&power 0>;
102 		required-opps = <&domain0_opp_0>;
105 	leaky-device1@12350000 {
106 		compatible = "foo,i-leak-current";
108 		power-domains = <&power 1>;
109 		required-opps = <&domain1_opp_1>;
112 [1]. Documentation/devicetree/bindings/power/domain-idle-state.yaml