diff options
author | Will Deacon <will@kernel.org> | 2021-06-08 17:43:40 +0200 |
---|---|---|
committer | Daniel Lezcano <daniel.lezcano@linaro.org> | 2021-08-13 09:24:22 +0200 |
commit | ae460fd9164b16654d8ec06cbc280b832f840eac (patch) | |
tree | 43fbb15aebe09c9a88bd0d9406e3118dcc4c263e /drivers/clocksource/timer-riscv.c | |
parent | hrtimer: Unbreak hrtimer_force_reprogram() (diff) | |
download | linux-ae460fd9164b16654d8ec06cbc280b832f840eac.tar.xz linux-ae460fd9164b16654d8ec06cbc280b832f840eac.zip |
clocksource/drivers/exynos_mct: Prioritise Arm arch timer on arm64
All arm64 CPUs feature an architected timer, which offers a relatively
low-latency interface to a per-cpu clocksource and timer. For the most
part, using this interface is a no-brainer, with the exception of SoCs
where it cannot be used to wake up from deep idle state (i.e.
CLOCK_EVT_FEAT_C3STOP is set).
On the contrary, the Exynos MCT is extremely slow to access yet can be
used as a wakeup source. In preparation for using the Exynos MCT as a
potential wakeup timer for the Arm architected timer, reduce its ratings
so that the architected timer is preferred.
This effectively reverts the decision made in 6282edb72bed
("clocksource/drivers/exynos_mct: Increase priority over ARM arch timer")
for arm64, as the reasoning for the original change was to work around
a 32-bit SoC design.
Cc: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Chanwoo Choi <cw00.choi@samsung.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Will Deacon <will@kernel.org>
Tested-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com> # exynos-5422
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20210608154341.10794-2-will@kernel.org
Diffstat (limited to 'drivers/clocksource/timer-riscv.c')
0 files changed, 0 insertions, 0 deletions