diff options
author | Hauke Mehrtens <hauke@hauke-m.de> | 2021-08-29 21:27:20 +0200 |
---|---|---|
committer | Hauke Mehrtens <hauke@hauke-m.de> | 2021-08-29 21:30:32 +0200 |
commit | 085c67762ddac7133b47c6e3825d944c41a5e174 (patch) | |
tree | 1a1ea9692ab0a35dbc98a69bbd68bda6957a7270 /target/linux/mvebu | |
parent | ff31cfb8569f87195a20450aa11e3bdcae59e25c (diff) | |
download | upstream-085c67762ddac7133b47c6e3825d944c41a5e174.tar.gz upstream-085c67762ddac7133b47c6e3825d944c41a5e174.tar.bz2 upstream-085c67762ddac7133b47c6e3825d944c41a5e174.zip |
kernel: bump 5.4 to 5.4.143
Manually rebased:
bcm27xx/patches-5.4/950-1031-net-lan78xx-Ack-pending-PHY-ints-when-resetting.patch
Removed upstreamed:
mvebu/patches-5.4/100-cpufreq-armada-37xx-forbid-cpufreq-for-1.2-GHz-variant.patch
All others updated automatically.
Compile-tested on: lantiq/xrx200, armvirt/64
Runtime-tested on: lantiq/xrx200, armvirt/64
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Diffstat (limited to 'target/linux/mvebu')
-rw-r--r-- | target/linux/mvebu/patches-5.4/100-cpufreq-armada-37xx-forbid-cpufreq-for-1.2-GHz-variant.patch | 39 |
1 files changed, 0 insertions, 39 deletions
diff --git a/target/linux/mvebu/patches-5.4/100-cpufreq-armada-37xx-forbid-cpufreq-for-1.2-GHz-variant.patch b/target/linux/mvebu/patches-5.4/100-cpufreq-armada-37xx-forbid-cpufreq-for-1.2-GHz-variant.patch deleted file mode 100644 index 6a5b8220f8..0000000000 --- a/target/linux/mvebu/patches-5.4/100-cpufreq-armada-37xx-forbid-cpufreq-for-1.2-GHz-variant.patch +++ /dev/null @@ -1,39 +0,0 @@ -From: =?utf-8?q?Marek_Beh=C3=BAn?= <kabel@kernel.org> -Subject: [PATCH v2] cpufreq: armada-37xx: forbid cpufreq for 1.2 GHz variant -Date: Thu, 1 Jul 2021 00:56:01 +0200 - -The 1.2 GHz variant of the Armada 3720 SOC is unstable with DVFS: when -the SOC boots, the WTMI firmware sets clocks and AVS values that work -correctly with 1.2 GHz CPU frequency, but random crashes occur once -cpufreq driver starts scaling. - -We do not know currently what is the reason: -- it may be that the voltage value for L0 for 1.2 GHz variant provided - by the vendor in the OTP is simply incorrect when scaling is used, -- it may be that some delay is needed somewhere, -- it may be something else. - -The most sane solution now seems to be to simply forbid the cpufreq -driver on 1.2 GHz variant. - -Signed-off-by: Marek BehĂșn <kabel@kernel.org> -Fixes: 92ce45fb875d ("cpufreq: Add DVFS support for Armada 37xx") ---- - drivers/cpufreq/armada-37xx-cpufreq.c | 6 +++++- - 1 file changed, 5 insertions(+), 1 deletion(-) - ---- a/drivers/cpufreq/armada-37xx-cpufreq.c -+++ b/drivers/cpufreq/armada-37xx-cpufreq.c -@@ -102,7 +102,11 @@ struct armada_37xx_dvfs { - }; - - static struct armada_37xx_dvfs armada_37xx_dvfs[] = { -- {.cpu_freq_max = 1200*1000*1000, .divider = {1, 2, 4, 6} }, -+ /* -+ * The cpufreq scaling for 1.2 GHz variant of the SOC is currently -+ * unstable because we do not know how to configure it properly. -+ */ -+ /* {.cpu_freq_max = 1200*1000*1000, .divider = {1, 2, 4, 6} }, */ - {.cpu_freq_max = 1000*1000*1000, .divider = {1, 2, 4, 5} }, - {.cpu_freq_max = 800*1000*1000, .divider = {1, 2, 3, 4} }, - {.cpu_freq_max = 600*1000*1000, .divider = {2, 4, 5, 6} }, |