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

commit af87a39a5f7cf6ef252b1aec3e2e6508a40e51f1 upstream.

These aren't used until now by any DT files and wouldn't be used now as
we have a better scheme in place now, i.e. opp-property-<name>
properties.

Remove the (useless) binding without breaking ABI.

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 | 62 +------------------
1 file changed, 2 insertions(+), 60 deletions(-)

diff --git a/Documentation/devicetree/bindings/opp/opp.txt b/Documentatio=
n/devicetree/bindings/opp/opp.txt
index a3e7f0d5e1fb4..24eac9a977494 100644
--- a/Documentation/devicetree/bindings/opp/opp.txt
+++ b/Documentation/devicetree/bindings/opp/opp.txt
@@ -45,21 +45,10 @@ Devices supporting OPPs must set their "operating-poi=
nts-v2" property with
phandle to a OPP table in their DT node. The OPP core will use this phan=
dle to
find the operating points for the device.
=20
-Devices may want to choose OPP tables at runtime and so can provide a li=
st of
-phandles here. But only *one* of them should be chosen at runtime. This =
must be
-accompanied by a corresponding "operating-points-names" property, to uni=
quely
-identify the OPP tables.
-
If required, this can be extended for SoC vendor specfic bindings. Such =
bindings
should be documented as Documentation/devicetree/bindings/power/<vendor>=
-opp.txt
and should have a compatible description like: "operating-points-v2-<ven=
dor>".
=20
-Optional properties:
-- operating-points-names: Names of OPP tables (required if multiple OPP
- tables are present), to uniquely identify them. The same list must be =
present
- for all the CPUs which are sharing clock/voltage rails and hence the O=
PP
- tables.
-
* OPP Table Node
=20
This describes the OPPs belonging to a device. This node can have follow=
ing
@@ -448,54 +437,7 @@ Example 4: Handling multiple regulators
};
};
=20
-Example 5: Multiple OPP tables
-
-/ {
- cpus {
- cpu@0 {
- compatible =3D "arm,cortex-a7";
- ...
-
- cpu-supply =3D <&cpu_supply>
- operating-points-v2 =3D <&cpu0_opp_table_slow>, <&cpu0_opp_table_fast=

;

- operating-points-names =3D "slow", "fast";
- };
- };
-
- cpu0_opp_table_slow: opp_table_slow {
- compatible =3D "operating-points-v2";
- status =3D "okay";
- opp-shared;
-
- opp00 {
- opp-hz =3D /bits/ 64 <600000000>;
- ...
- };
-
- opp01 {
- opp-hz =3D /bits/ 64 <800000000>;
- ...
- };
- };
-
- cpu0_opp_table_fast: opp_table_fast {
- compatible =3D "operating-points-v2";
- status =3D "okay";
- opp-shared;
-
- opp10 {
- opp-hz =3D /bits/ 64 <1000000000>;
- ...
- };
-
- opp11 {
- opp-hz =3D /bits/ 64 <1100000000>;
- ...
- };
- };
-};
-
-Example 6: opp-supported-hw
+Example 5: opp-supported-hw
(example: three level hierarchy of versions: cuts, substrate and process=
)
=20
/ {
@@ -540,7 +482,7 @@ Example 6: opp-supported-hw
};
};
=20
-Example 7: opp-microvolt-<name>, opp-microamp-<name>:
+Example 6: opp-microvolt-<name>, opp-microamp-<name>:
(example: device with two possible microvolt ranges: slow and fast)
=20
/ {
--=20
2.27.0.rc0