ARM: OMAP2+: Add and enable operating-points-v2

After the ti-cpufreq driver has been added, we can now drop the operating-points table present in am33xx.dtsi for the cpu and add an operating-points-v2 table with all OPPs available for all silicon revisions. Also add necessary data for use by ti-cpufreq to selectively enable the appropriate OPPs at runtime as part of the operating-points table.

Information from AM335x Data Manual, SPRS717i, Revised December 2015, Table 5-7.

Signed-off-by Dave Gerlach <[email protected]>

Although all PG2.0 silicon may not support 1GHz OPP for the MPU, older Beaglebone Blacks may have PG2.0 silicon populated and these particular parts are guaranteed to support the OPP, so enable it for PG2.0 on am335x-boneblack only.

Signed-off-by Dave Gerlach <[email protected]>

---
 arch/arm/boot/dts/am335x-boneblack.dts | 11 +++++++++++
 1 file changed, 11 insertions(+)

(quoted diff) +0 -0

b/arch/arm/boot/dts/am335x-boneblack.dts index 77273df1a028..935ed17d22e4 100644 --- a/arch/arm/boot/dts/am335x-boneblack.dts +++ b/arch/arm/boot/dts/am335x-boneblack.dts @@ -15,3 +15,14 @@

(quoted diff) +0 -0

 	model = "TI AM335x BeagleBone Black";
 	compatible = "ti,am335x-bone-black", "ti,am335x-bone",

"ti,am33xx"; };

arch/arm/boot/dts/am335x-boneblack.dts +4 -0

+
+&cpu0_opp_table {
+	/*
+	 * All PG 2.0 silicon may not support 1GHz but some of the

early

The operatings-points-v2 table for am4372 was merged before any user of it was present in the kernel and before the binding had been finalized. The new ti-cpufreq driver and binding expects the platform specific properties to be part of the operating-points-v2 table rather than the cpu node so let's move them there as the only user is the ti-cpufreq driver.

Signed-off-by Dave Gerlach <[email protected]>

---
 arch/arm/boot/dts/am4372.dtsi | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

(quoted diff) +0 -0

b/arch/arm/boot/dts/am4372.dtsi index 97fcaf415de1..176e09e9a45e 100644 --- a/arch/arm/boot/dts/am4372.dtsi
+++ b/arch/arm/boot/dts/am4372.dtsi

arch/arm/boot/dts/am4372.dtsi +0 -2

@@ -50,15 +50,14 @@
 			clock-names = "cpu";
 
 			operating-points-v2 = <&cpu0_opp_table>;
-			ti,syscon-efuse = <&scm_conf 0x610 0x3f 0>;
-			ti,syscon-rev = <&scm_conf 0x600>;
 
 			clock-latency = <300000>; /* From
 omap-cpufreq driver */ };

After the ti-cpufreq driver has been added, we can now drop the operating-points table present in dra7.dtsi for the cpu and add an operating-points-v2 table with all OPPs available for all silicon revisions. Also add necessary data for use by ti-cpufreq to selectively enable the appropriate OPPs at runtime as part of the operating-points table.

As we now need to define voltage ranges for each OPP, we define the minimum and maximum voltage to match the ranges possible for AVS class0 voltage as defined by the DRA7/AM57 Data Manual, with the exception of using a range for OPP_OD based on historical data to ensure that SoCs from older lots still continue to boot, even though more optimal voltages are now the standard. Once an AVS Class0 driver is in place it will be possible for these OPP voltages to be adjusted to any voltage within the provided range.

Information from SPRS953, Revised December 2015.

Signed-off-by Dave Gerlach <[email protected]>

---
 arch/arm/boot/dts/dra7.dtsi   | 24 +++++++++++++++++++-----
 arch/arm/boot/dts/dra74x.dtsi |  5 +++++
 2 files changed, 24 insertions(+), 5 deletions(-)

arch/arm/boot/dts/dra7.dtsi +19 -5

index 2c9e56f4aac5..e9dc314b0dcf 100644
@@ -81,11 +81,7 @@
 			compatible = "arm,cortex-a15";
 			reg = <0>;
 
-			operating-points = <
-				/* kHz    uV */
-				1000000	1060000
-				1176000	1160000
-				>;
+			operating-points-v2 = <&cpu0_opp_table>;
 
 			clocks = <&dpll_mpu_ck>;
 			clock-names = "cpu";

@@ -99,6 +95,24 @@
 		};
 	};
 
+	cpu0_opp_table: opp-table {
+		compatible = "operating-points-v2-ti-cpu";
+		syscon = <&scm_wkup>;
+
+		opp_nom at 1000000000 {
+			opp-hz = /bits/ 64 <1000000000>;
+			opp-microvolt = <1060000 850000 1150000>;
+			opp-supported-hw = <0xFF 0x01>;
+			opp-suspend;
+		};
+
+		opp_od at 1176000000 {
+			opp-hz = /bits/ 64 <1176000000>;
+			opp-microvolt = <1160000 885000 1160000>;
+			opp-supported-hw = <0xFF 0x02>;
+		};
+	};
+
 	/*
 	 * The soc node represents the soc top level view. It is

used for IPs
* that are not memory mapped in the MPU view or for the MPU
itself. diff --git a/arch/arm/boot/dts/dra74x.dtsi b/arch/arm/boot/dts/dra74x.dtsi index 0a78347e6615..24e6746c5b26 100644 --- a/arch/arm/boot/dts/dra74x.dtsi
+++ b/arch/arm/boot/dts/dra74x.dtsi

arch/arm/boot/dts/dra7.dtsi +1 -0

@@ -17,6 +17,7 @@
 			device_type = "cpu";
 			compatible = "arm,cortex-a15";
 			reg = <1>;
+			operating-points-v2 = <&cpu0_opp_table>;
 		};
 	};
 

AM335x, AM437x, DRA7xx, and AM57xx platforms all now depend on ti-cpufreq driver to enable proper OPPs for use with cpufreq, so enable the same.

Signed-off-by Dave Gerlach <[email protected]>

---
 arch/arm/configs/omap2plus_defconfig | 1 +
 1 file changed, 1 insertion(+)

(quoted diff) +0 -0

b/arch/arm/configs/omap2plus_defconfig index f2462a6bdba6..62a4b6cf16f0 100644 --- a/arch/arm/configs/omap2plus_defconfig +++ b/arch/arm/configs/omap2plus_defconfig @@ -64,6 +64,7 @@ CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y CONFIG_CPUFREQ_DT=m
+CONFIG_ARM_TI_CPUFREQ=y
# CONFIG_ARM_OMAP2PLUS_CPUFREQ is not set CONFIG_CPU_IDLE=y
CONFIG_BINFMT_MISC=y

Hi,
This series adds the necessary changes to get proper operating-points-v2 tables for AM335x/AM437x/DRA7xx/AM57xx TI SoCs. Doing this enables the ti-cpufreq driver and allows the platform to detect which CPU OPPs are valid for the configuration in use and enable them.

This series adds complete tables for am335x and adds 1GHz support for all beaglebone black boards and updates the already merged but unused am437x table to match the finalized DT bindings. It also moves the existing dra7xx/am57xx OPPs to OPPv2 but does not enable 1.5GHz yet as this requires multiregulator support which will come at a later date.

Also, now that so many TI platforms will depend on the ti-cpufreq driver let's add CONFIG_ARM_TI_CPUFREQ to omap2plus_defconfig to enable it as part of the default configuration.

Pushed a branch containing these patches on top of v4.11-rc1 if anyone wants to try it out [1].

Hi,
This series adds the necessary changes to get proper operating-points-v2 tables for AM335x/AM437x/DRA7xx/AM57xx TI SoCs. Doing this enables the ti-cpufreq driver and allows the platform to detect which CPU OPPs are valid for the configuration in use and enable them.

This series adds complete tables for am335x and adds 1GHz support for all beaglebone black boards and updates the already merged but unused am437x table to match the finalized DT bindings. It also moves the existing dra7xx/am57xx OPPs to OPPv2 but does not enable 1.5GHz yet as this requires multiregulator support which will come at a later date.

Also, now that so many TI platforms will depend on the ti-cpufreq driver let's add CONFIG_ARM_TI_CPUFREQ to omap2plus_defconfig to enable it as part of the default configuration.