ARM: dts: OMAP5: Update CPU OPP table as per final production Manual
PATCH 1/1 ARM: dts: OMAP5: Update CPU OPP table as per final production Manual
As per the Final production Data Manual for OMAP5432, SWPS050F(APRIL 2014)
There are only two OPPs - 1GHz and 1.5GHz. the older OPP_LOW has been completely descoped. The Nominal voltages are still correct though. However, expectation for final production configuration is operation with Adaptive Body Bias (ABB) and Adaptive Voltage Scaling Class 0 operation.
There are no IDcode or version change information encoded to programmatically detect this and software is supposed to NOT use OPP_LOW(500MHz) anymore for all devices (legacy and production samples).
--- arch/arm/boot/dts/omap5.dtsi | 1 - 1 file changed, 1 deletion(-)
arch/arm/boot/dts/omap5.dtsi +0 -1
@@ -45,7 +45,6 @@ operating-points = < /* kHz uV */ - 500000 880000 1000000 1060000 1500000 1250000 >;
Signature · 1 line
1.7.9.5
PATCH 1/1 ARM: dts: OMAP5: Update CPU OPP table as per final production Manual
Quoted 9 lines · Nishanth Menon
As per the Final production Data Manual for OMAP5432, SWPS050F(APRIL 2014)
There are only two OPPs - 1GHz and 1.5GHz. the older
OPP_LOWhas been completely descoped. The Nominal voltages are still correct though. However, expectation for final production configuration is operation with Adaptive Body Bias (ABB) and Adaptive Voltage Scaling Class 0 operation.
Quoted 6 lines
There are no IDcode or version change information encoded to programmatically detect this and software is supposed to NOT use
OPP_LOW(500MHz)anymore for all devices (legacy and production samples).Signed-off-by Nishanth Menon <[email protected]>
Thanks applying into omap-for-v3.16/fixes.
Tony
Quoted 19 lines
--- arch/arm/boot/dts/omap5.dtsi | 1 - 1 file changed, 1 deletion(-)arch/arm/boot/dts/omap5.dtsi +0
-1@@ -45,7 +45,6 @@ operating-points = < /* kHz uV */ - 500000 880000 1000000 1060000 1500000 1250000 >;Signature · 1 line
1.7.9.5