aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm64/boot/dts/rockchip/px30.dtsi
diff options
context:
space:
mode:
authorHeiko Stuebner <heiko.stuebner@theobroma-systems.com>2019-11-16 10:52:20 +0100
committerHeiko Stuebner <heiko@sntech.de>2019-12-09 09:44:22 +0100
commit8554723e664d8ac2a0e2e07c81e88cd15b75b0c6 (patch)
tree231110cc03f9ad38890a05ccab9b94b92abf4e26 /arch/arm64/boot/dts/rockchip/px30.dtsi
parentarm64: dts: rockchip: Improve nanopi4 PCIe (diff)
downloadlinux-dev-8554723e664d8ac2a0e2e07c81e88cd15b75b0c6.tar.xz
linux-dev-8554723e664d8ac2a0e2e07c81e88cd15b75b0c6.zip
arm64: dts: rockchip: remove 408MHz operating point from px30
It looks like the px30 is running unstable at this 408MHz operating point. This shows in stalled threads and other big numbers of kernel exception. At 600MHz and above it instead works stable and as expected. As the 408MHz point doesn't even decrease the voltage compared to 600MHz, just drop this 408MHz operating point for now. Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com> Link: https://lore.kernel.org/r/20191116095220.31122-1-heiko@sntech.de
Diffstat (limited to '')
-rw-r--r--arch/arm64/boot/dts/rockchip/px30.dtsi7
1 files changed, 1 insertions, 6 deletions
diff --git a/arch/arm64/boot/dts/rockchip/px30.dtsi b/arch/arm64/boot/dts/rockchip/px30.dtsi
index 8812b70f3911..633eb917220a 100644
--- a/arch/arm64/boot/dts/rockchip/px30.dtsi
+++ b/arch/arm64/boot/dts/rockchip/px30.dtsi
@@ -113,16 +113,11 @@
compatible = "operating-points-v2";
opp-shared;
- opp-408000000 {
- opp-hz = /bits/ 64 <408000000>;
- opp-microvolt = <950000 950000 1350000>;
- clock-latency-ns = <40000>;
- opp-suspend;
- };
opp-600000000 {
opp-hz = /bits/ 64 <600000000>;
opp-microvolt = <950000 950000 1350000>;
clock-latency-ns = <40000>;
+ opp-suspend;
};
opp-816000000 {
opp-hz = /bits/ 64 <816000000>;