summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
diff options
context:
space:
mode:
authorMarek Szyprowski <m.szyprowski@samsung.com>2018-03-21 10:45:05 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-04-24 09:36:24 +0200
commit2106cd34635e5aa95d759e414e38d5fd216ce8ec (patch)
tree117fedfaf87e0669e259334946e347f6cf9cbd94 /arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
parent326e61ce9761d71098c7001e51dafec067f50424 (diff)
ARM: EXYNOS: Fix coupled CPU idle freeze on Exynos4210
commit a7480dbcf983c31d8111f864c848e8a75116a87d upstream. Since commit 04c8b0f82c7d ("irqchip/gic: Make locking a BL_SWITCHER only feature") coupled CPU idle freezes from time to time on Exynos4210. Later commit 313c8c16ee62 ("PM / CPU: replace raw_notifier with atomic_notifier") changed the context in which the CPU idle code is executed, what results in fully reproducible freeze all the time. However, almost the same coupled CPU idle code works fine on Exynos3250 regardless of the changes made in the mentioned commits. It turned out that the IPI call used on Exynos4210 is conflicting with the change done in the first mentioned commit in GIC. Fix this by using the same code path as for Exynos3250, instead of the IPI call for synchronization with second CPU core, call dsb_sev() directly. Tested on Exynos4210-based Trats and Origen boards. Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> CC: <stable@vger.kernel.org> # v4.13+ Acked-by: Marc Zyngier <marc.zyngier@arm.com> Acked-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts')
0 files changed, 0 insertions, 0 deletions