clocksource/drivers/arm_arch_timer: Don't assume clock runs in suspend
authorBrian Norris <briannorris@chromium.org>
Tue, 4 Oct 2016 18:12:09 +0000 (11:12 -0700)
committerDaniel Lezcano <daniel.lezcano@linaro.org>
Mon, 21 Nov 2016 10:05:36 +0000 (11:05 +0100)
commitd8ec7595a013237f82d965dcf981571aeb41855b
tree098c25d78acbd3aa0f22a06c131fef47b674b692
parentbaa73d9e478ff32d62f3f9422822b59dd9a95a21
clocksource/drivers/arm_arch_timer: Don't assume clock runs in suspend

The ARM specifies that the system counter "must be implemented in an
always-on power domain," and so we try to use the counter as a source of
timekeeping across suspend/resume. Unfortunately, some SoCs (e.g.,
Rockchip's RK3399) do not keep the counter ticking properly when
switched from their high-power clock to the lower-power clock used in
system suspend. Support this quirk by adding a new device tree property.

Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Documentation/devicetree/bindings/arm/arch_timer.txt
drivers/clocksource/arm_arch_timer.c