aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--Documentation/devicetree/bindings/power/power_domain.txt19
1 files changed, 14 insertions, 5 deletions
diff --git a/Documentation/devicetree/bindings/power/power_domain.txt b/Documentation/devicetree/bindings/power/power_domain.txt
index 4733f76cbe48..9b387f861aed 100644
--- a/Documentation/devicetree/bindings/power/power_domain.txt
+++ b/Documentation/devicetree/bindings/power/power_domain.txt
@@ -111,8 +111,8 @@ Example 3:
111==PM domain consumers== 111==PM domain consumers==
112 112
113Required properties: 113Required properties:
114 - power-domains : A phandle and PM domain specifier as defined by bindings of 114 - power-domains : A list of PM domain specifiers, as defined by bindings of
115 the power controller specified by phandle. 115 the power controller that is the PM domain provider.
116 116
117Example: 117Example:
118 118
@@ -122,9 +122,18 @@ Example:
122 power-domains = <&power 0>; 122 power-domains = <&power 0>;
123 }; 123 };
124 124
125The node above defines a typical PM domain consumer device, which is located 125 leaky-device@12351000 {
126inside a PM domain with index 0 of a power controller represented by a node 126 compatible = "foo,i-leak-current";
127with the label "power". 127 reg = <0x12351000 0x1000>;
128 power-domains = <&power 0>, <&power 1> ;
129 };
130
131The first example above defines a typical PM domain consumer device, which is
132located inside a PM domain with index 0 of a power controller represented by a
133node with the label "power".
134In the second example the consumer device are partitioned across two PM domains,
135the first with index 0 and the second with index 1, of a power controller that
136is represented by a node with the label "power.
128 137
129Optional properties: 138Optional properties:
130- required-opps: This contains phandle to an OPP node in another device's OPP 139- required-opps: This contains phandle to an OPP node in another device's OPP