Message ID | 20210109170103.1249838-1-aford173@gmail.com |
---|---|
State | Accepted |
Commit | 5f1bf7ae848104b7cb589e03a9bbef61a9a62612 |
Headers | show |
Series |
|
Related | show |
* Adam Ford <aford173@gmail.com> [210109 19:01]: > Previously, the 1GHz variants were marked as a turbo, > because that variant has reduced thermal operating range. > > Now that the thermal throttling is in place, it should be > safe to remove the turbo-mode from the 1GHz variants, because > the CPU will automatically slow if the thermal limit is reached. Thanks applying into omap-for-v5.12/dt. Tony
diff --git a/arch/arm/boot/dts/omap36xx.dtsi b/arch/arm/boot/dts/omap36xx.dtsi index 05fe5ed127b0..20844dbc002e 100644 --- a/arch/arm/boot/dts/omap36xx.dtsi +++ b/arch/arm/boot/dts/omap36xx.dtsi @@ -72,7 +72,6 @@ opp1g-1000000000 { <1375000 1375000 1375000>; /* only on am/dm37x with speed-binned bit set */ opp-supported-hw = <0xffffffff 2>; - turbo-mode; }; };
Previously, the 1GHz variants were marked as a turbo, because that variant has reduced thermal operating range. Now that the thermal throttling is in place, it should be safe to remove the turbo-mode from the 1GHz variants, because the CPU will automatically slow if the thermal limit is reached. Signed-off-by: Adam Ford <aford173@gmail.com> --- V2: The orignal patch had the wrong file added. Add the omap36xx.dtsi