summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/opp
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2018-01-05 12:57:19 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2018-01-05 12:57:19 +0100
commitb68bf11ebb536ee77c78baa56793b297212a38cd (patch)
treec2b9aa19ccf2344f56a124f6a032f4108f3436c6 /Documentation/devicetree/bindings/opp
parent30a7acd573899fd8b8ac39236eff6468b195ac7d (diff)
parente856f078bcf120e1627c750014d2612974ed81a2 (diff)
Merge branch 'opp/linux-next' of https://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm
Pull Operating Performance Points (OPP) framework updates for v4.16 from Viresh Kumar. * 'opp/linux-next' of https://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
Diffstat (limited to 'Documentation/devicetree/bindings/opp')
-rw-r--r--Documentation/devicetree/bindings/opp/opp.txt13
1 files changed, 13 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/opp/opp.txt b/Documentation/devicetree/bindings/opp/opp.txt
index 9d733af26be7..4e4f30288c8b 100644
--- a/Documentation/devicetree/bindings/opp/opp.txt
+++ b/Documentation/devicetree/bindings/opp/opp.txt
@@ -45,6 +45,11 @@ Devices supporting OPPs must set their "operating-points-v2" property with
phandle to a OPP table in their DT node. The OPP core will use this phandle to
find the operating points for the device.
+This can contain more than one phandle for power domain providers that provide
+multiple power domains. That is, one phandle for each power domain. If only one
+phandle is available, then the same OPP table will be used for all power domains
+provided by the power domain provider.
+
If required, this can be extended for SoC vendor specific bindings. Such bindings
should be documented as Documentation/devicetree/bindings/power/<vendor>-opp.txt
and should have a compatible description like: "operating-points-v2-<vendor>".
@@ -154,6 +159,14 @@ Optional properties:
- status: Marks the node enabled/disabled.
+- required-opp: This contains phandle to an OPP node in another device's OPP
+ table. It may contain an array of phandles, where each phandle points to an
+ OPP of a different device. It should not contain multiple phandles to the OPP
+ nodes in the same OPP table. This specifies the minimum required OPP of the
+ device(s), whose OPP's phandle is present in this property, for the
+ functioning of the current device at the current OPP (where this property is
+ present).
+
Example 1: Single cluster Dual-core ARM cortex A9, switch DVFS states together.
/ {