summaryrefslogtreecommitdiff
path: root/ipc
diff options
context:
space:
mode:
authorBrian Norris <briannorris@chromium.org>2017-04-04 19:32:05 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-04-12 10:41:16 (GMT)
commit26cbe162df3d0282e5108711663b8dcdafb1ad33 (patch)
treec8dd2fc66bb25fc646f349c6cae47b1b18829e28 /ipc
parentd2f1000c3ae3ce285d99dae444f85baa53c1dfe6 (diff)
downloadlinux-26cbe162df3d0282e5108711663b8dcdafb1ad33.tar.xz
clocksource/drivers/arm_arch_timer: Don't assume clock runs in suspend
[ Upstream commit d8ec7595a013237f82d965dcf981571aeb41855b ] 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> Signed-off-by: Sasha Levin <alexander.levin@verizon.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'ipc')
0 files changed, 0 insertions, 0 deletions