summaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorOlof Johansson <olof@lixom.net>2017-12-03 19:28:33 -0800
committerOlof Johansson <olof@lixom.net>2017-12-03 19:39:22 -0800
commit81faa5566864e97a5578c4e08c07edf04239abcc (patch)
treef104d4891f39cd2f769458121d2d7ae4044a711e /arch
parent0d55f2ab0dc479ce4b6bcc58beec6b63b630ff05 (diff)
downloadlinux-stable-81faa5566864e97a5578c4e08c07edf04239abcc.tar.gz
linux-stable-81faa5566864e97a5578c4e08c07edf04239abcc.tar.bz2
linux-stable-81faa5566864e97a5578c4e08c07edf04239abcc.zip
firmware: arm_scpi: Revert updates made during v4.15 merge window
Revert "Merge tag 'scpi-updates-4.15' of git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux into next/drivers" Paraphrased from email from Kevin Hilman: Revert ARM SCPI changes since v4.14. Untested changes caused regressions in SCPI and CPUfreq/DVFS failures on most Amlogic SoCs. Changes reverted for v4.15 so they can be better reviewed and tested. These ARM SCPI changes caused SCPI regressions resulting in CPUfreq failures on most Amlogic SoCs (found by kernelci.org.) Unfortunately, this was not caught in linux-next due to other bugs/panics on these platforms masking this problem so we've only found it since we've fixed the other issues. Since we're already in the -rc cycle, I'd prefer to revert to a known working state (that of v4.14) rather than finding/reverting a subset, which would just lead to another untested state. These changes can then have some time to be better reviewed and tested and resubmitted for v4.16. Kevin Hilman has tested this revert on the affected Amlogic SoCs and verified that we're back to the previous (working) condition. This reverts commit 6710acf2596a29f7351e8165d981645f403e0025, reversing changes made to 4b367f2e8854da34d14bd154ff4432fb49f69b36. Reported-by: Kevin Hilman <khilman@baylibre.com> Signed-off-by: Olof Johansson <olof@lixom.net>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions