[4.4.y-cip 02/15] PM / OPP: Add "opp-supported-hw" binding


Chen-Yu Tsai (Moxa) <wens@...>
 

From: Viresh Kumar <viresh.kumar@...>

commit 1c4d12de2719dfdf27c6dab31e7a5641ee293c94 upstream.

We may want to enable only a subset of OPPs, from the bigger list of
OPPs, based on what version of the hardware we are running on. This
would enable us to not duplicate OPP tables for every version of the
hardware we support.

To enable that, this patch defines a new property 'opp-supported-hw'. It
can support any number of hierarchy levels of the versions the hardware
follows. And based on the selected hardware versions, we can pick only
the relevant OPPs at runtime.

Reviewed-by: Stephen Boyd <sboyd@...>
Acked-by: Rob Herring <robh@...>
Signed-off-by: Viresh Kumar <viresh.kumar@...>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...>
Signed-off-by: Chen-Yu Tsai (Moxa) <wens@...>
---
Documentation/devicetree/bindings/opp/opp.txt | 65 +++++++++++++++++++
1 file changed, 65 insertions(+)

diff --git a/Documentation/devicetree/bindings/opp/opp.txt b/Documentatio=
n/devicetree/bindings/opp/opp.txt
index 0cb44dc21f97c..d072fa0ffbd44 100644
--- a/Documentation/devicetree/bindings/opp/opp.txt
+++ b/Documentation/devicetree/bindings/opp/opp.txt
@@ -123,6 +123,26 @@ Optional properties:
- opp-suspend: Marks the OPP to be used during device suspend. Only one =
OPP in
the table should have this.
=20
+- opp-supported-hw: This enables us to select only a subset of OPPs from=
the
+ larger OPP table, based on what version of the hardware we are running=
on. We
+ still can't have multiple nodes with the same opp-hz value in OPP tabl=
e.
+
+ It's an user defined array containing a hierarchy of hardware version =
numbers,
+ supported by the OPP. For example: a platform with hierarchy of three =
levels
+ of versions (A, B and C), this field should be like <X Y Z>, where X
+ corresponds to Version hierarchy A, Y corresponds to version hierarchy=
B and Z
+ corresponds to version hierarchy C.
+
+ Each level of hierarchy is represented by a 32 bit value, and so there=
can be
+ only 32 different supported version per hierarchy. i.e. 1 bit per vers=
ion. A
+ value of 0xFFFFFFFF will enable the OPP for all versions for that hier=
archy
+ level. And a value of 0x00000000 will disable the OPP completely, and =
so we
+ never want that to happen.
+
+ If 32 values aren't sufficient for a version hierarchy, than that vers=
ion
+ hierarchy can be contained in multiple 32 bit values. i.e. <X Y Z1 Z2>=
in the
+ above example, Z1 & Z2 refer to the version hierarchy Z.
+
- status: Marks the node enabled/disabled.
=20
Example 1: Single cluster Dual-core ARM cortex A9, switch DVFS states to=
gether.
@@ -463,3 +483,48 @@ Example 5: Multiple OPP tables
};
};
};
+
+Example 6: opp-supported-hw
+(example: three level hierarchy of versions: cuts, substrate and process=
)
+
+/ {
+ cpus {
+ cpu@0 {
+ compatible =3D "arm,cortex-a7";
+ ...
+
+ cpu-supply =3D <&cpu_supply>
+ operating-points-v2 =3D <&cpu0_opp_table_slow>;
+ };
+ };
+
+ opp_table {
+ compatible =3D "operating-points-v2";
+ status =3D "okay";
+ opp-shared;
+
+ opp00 {
+ /*
+ * Supports all substrate and process versions for 0xF
+ * cuts, i.e. only first four cuts.
+ */
+ opp-supported-hw =3D <0xF 0xFFFFFFFF 0xFFFFFFFF>
+ opp-hz =3D /bits/ 64 <600000000>;
+ opp-microvolt =3D <900000 915000 925000>;
+ ...
+ };
+
+ opp01 {
+ /*
+ * Supports:
+ * - cuts: only one, 6th cut (represented by 6th bit).
+ * - substrate: supports 16 different substrate versions
+ * - process: supports 9 different process versions
+ */
+ opp-supported-hw =3D <0x20 0xff0000ff 0x0000f4f0>
+ opp-hz =3D /bits/ 64 <800000000>;
+ opp-microvolt =3D <900000 915000 925000>;
+ ...
+ };
+ };
+};
--=20
2.27.0.rc0