diff options
author | Will Deacon <[email protected]> | 2021-06-08 16:43:40 +0100 |
---|---|---|
committer | Daniel Lezcano <[email protected]> | 2021-08-13 09:24:22 +0200 |
commit | ae460fd9164b16654d8ec06cbc280b832f840eac (patch) | |
tree | 43fbb15aebe09c9a88bd0d9406e3118dcc4c263e /lib/test_overflow.c | |
parent | f80e21489590c00f46226d5802d900e6f66e5633 (diff) |
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 <[email protected]>
Cc: Krzysztof Kozlowski <[email protected]>
Cc: Chanwoo Choi <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Signed-off-by: Will Deacon <[email protected]>
Tested-by: Krzysztof Kozlowski <[email protected]> # exynos-5422
Signed-off-by: Daniel Lezcano <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'lib/test_overflow.c')
0 files changed, 0 insertions, 0 deletions