Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings
forked fromtorvalds/linux

Commitb68bf11

Browse files
committed
Pull Operating Performance Points (OPP) framework updates for v4.16from Viresh Kumar.* 'opp/linux-next' ofhttps://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm: OPP: Introduce "required-opp" property OPP: Allow OPP table to be used for power-domains
2 parents30a7acd +e856f07 commitb68bf11

File tree

2 files changed

+78
-0
lines changed

2 files changed

+78
-0
lines changed

‎Documentation/devicetree/bindings/opp/opp.txt‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,11 @@ Devices supporting OPPs must set their "operating-points-v2" property with
4545
phandle to a OPP table in their DT node. The OPP core will use this phandle to
4646
find the operating points for the device.
4747

48+
This can contain more than one phandle for power domain providers that provide
49+
multiple power domains. That is, one phandle for each power domain. If only one
50+
phandle is available, then the same OPP table will be used for all power domains
51+
provided by the power domain provider.
52+
4853
If required, this can be extended for SoC vendor specific bindings. Such bindings
4954
should be documented as Documentation/devicetree/bindings/power/<vendor>-opp.txt
5055
and should have a compatible description like: "operating-points-v2-<vendor>".
@@ -154,6 +159,14 @@ Optional properties:
154159

155160
- status: Marks the node enabled/disabled.
156161

162+
- required-opp: This contains phandle to an OPP node in another device's OPP
163+
table. It may contain an array of phandles, where each phandle points to an
164+
OPP of a different device. It should not contain multiple phandles to the OPP
165+
nodes in the same OPP table. This specifies the minimum required OPP of the
166+
device(s), whose OPP's phandle is present in this property, for the
167+
functioning of the current device at the current OPP (where this property is
168+
present).
169+
157170
Example 1: Single cluster Dual-core ARM cortex A9, switch DVFS states together.
158171

159172
/ {

‎Documentation/devicetree/bindings/power/power_domain.txt‎

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,12 @@ Optional properties:
4040
domain's idle states. In the absence of this property, the domain would be
4141
considered as capable of being powered-on or powered-off.
4242

43+
- operating-points-v2 : Phandles to the OPP tables of power domains provided by
44+
a power domain provider. If the provider provides a single power domain only
45+
or all the power domains provided by the provider have identical OPP tables,
46+
then this shall contain a single phandle. Refer to ../opp/opp.txt for more
47+
information.
48+
4349
Example:
4450

4551
power: power-controller@12340000 {
@@ -120,4 +126,63 @@ The node above defines a typical PM domain consumer device, which is located
120126
inside a PM domain with index 0 of a power controller represented by a node
121127
with the label "power".
122128

129+
Optional properties:
130+
- required-opp: This contains phandle to an OPP node in another device's OPP
131+
table. It may contain an array of phandles, where each phandle points to an
132+
OPP of a different device. It should not contain multiple phandles to the OPP
133+
nodes in the same OPP table. This specifies the minimum required OPP of the
134+
device(s), whose OPP's phandle is present in this property, for the
135+
functioning of the current device at the current OPP (where this property is
136+
present).
137+
138+
Example:
139+
- OPP table for domain provider that provides two domains.
140+
141+
domain0_opp_table: opp-table0 {
142+
compatible = "operating-points-v2";
143+
144+
domain0_opp_0: opp-1000000000 {
145+
opp-hz = /bits/ 64 <1000000000>;
146+
opp-microvolt = <975000 970000 985000>;
147+
};
148+
domain0_opp_1: opp-1100000000 {
149+
opp-hz = /bits/ 64 <1100000000>;
150+
opp-microvolt = <1000000 980000 1010000>;
151+
};
152+
};
153+
154+
domain1_opp_table: opp-table1 {
155+
compatible = "operating-points-v2";
156+
157+
domain1_opp_0: opp-1200000000 {
158+
opp-hz = /bits/ 64 <1200000000>;
159+
opp-microvolt = <975000 970000 985000>;
160+
};
161+
domain1_opp_1: opp-1300000000 {
162+
opp-hz = /bits/ 64 <1300000000>;
163+
opp-microvolt = <1000000 980000 1010000>;
164+
};
165+
};
166+
167+
power: power-controller@12340000 {
168+
compatible = "foo,power-controller";
169+
reg = <0x12340000 0x1000>;
170+
#power-domain-cells = <1>;
171+
operating-points-v2 = <&domain0_opp_table>, <&domain1_opp_table>;
172+
};
173+
174+
leaky-device0@12350000 {
175+
compatible = "foo,i-leak-current";
176+
reg = <0x12350000 0x1000>;
177+
power-domains = <&power 0>;
178+
required-opp = <&domain0_opp_0>;
179+
};
180+
181+
leaky-device1@12350000 {
182+
compatible = "foo,i-leak-current";
183+
reg = <0x12350000 0x1000>;
184+
power-domains = <&power 1>;
185+
required-opp = <&domain1_opp_1>;
186+
};
187+
123188
[1]. Documentation/devicetree/bindings/power/domain-idle-state.txt

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp