aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/gemini
diff options
context:
space:
mode:
authorJosef Schlehofer <pepe.schlehofer@gmail.com>2021-07-27 13:22:30 +0200
committerHauke Mehrtens <hauke@hauke-m.de>2021-08-08 19:50:45 +0200
commit7b868fe04a8961048feec1143e72fe47bde52a12 (patch)
treef9ad27a05d040ddce28aaf2533a8f77460559cea /target/linux/gemini
parent82620cd610807da73935832e3751771866faa7c9 (diff)
downloadupstream-7b868fe04a8961048feec1143e72fe47bde52a12.tar.gz
upstream-7b868fe04a8961048feec1143e72fe47bde52a12.tar.bz2
upstream-7b868fe04a8961048feec1143e72fe47bde52a12.zip
Revert "mvebu: 5.4 fix DVFS caused random boot crashes"
Based on the discussion on the mailing list [1], the patch which was reverted, it reverts only one patch without the subsequent ones. This leads to the SoC scaling issue not using a CPU parent clock, but it uses DDR clock. This is done for all variants, and it's wrong because commits (hacks) that were using the DDR clock are no longer in the mainline kernel. If someone has stability issues on 1.2 GHz, it should not affect all routers (1 GHz, 800 MHz) and it should be rather consulted with guys, who are trying to improve the situation in the kernel and not making the situation worse. There are two solutions in cases of instability: a) disable cpufreq b) underclock it up to 1 GHz This reverts commit 080a0b74e39d159eecf69c468debec42f28bf4d8. [1] https://lists.openwrt.org/pipermail/openwrt-devel/2021-June/035702.html CC: Pali Rohár <pali@kernel.org> Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
Diffstat (limited to 'target/linux/gemini')
0 files changed, 0 insertions, 0 deletions