arch_timer: Move to generic sched_clock framework
authorStephen Boyd <sboyd@codeaurora.org>
Thu, 18 Jul 2013 23:21:18 +0000 (16:21 -0700)
committerAjay Nandakumar <anandakumarm@nvidia.com>
Mon, 13 Jan 2014 06:33:37 +0000 (11:33 +0530)
commit6220dca122e5d31ff3a167d14680e424664b8c7a
tree4082e26409646a83a22b410ac1ba1fa0028addff
parent9677b59f55e348c330eeb8cd9a6f7b2f613839a5
arch_timer: Move to generic sched_clock framework

Register with the generic sched_clock framework now that it
supports 64 bits. This fixes two problems with the current
sched_clock support for machines using the architected timers.
First off, we don't subtract the start value from subsequent
sched_clock calls so we can potentially start off with
sched_clock returning gigantic numbers. Second, there is no
support for suspend/resume handling so problems such as discussed
in 6a4dae5 (ARM: 7565/1: sched: stop sched_clock() during
suspend, 2012-10-23) can happen without this patch. Finally, it
allows us to move the sched_clock setup into drivers clocksource
out of the arch ports.

Bug 1399318

Cc: Christopher Covington <cov@codeaurora.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Acked-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: John Stultz <john.stultz@linaro.org>
(cherry picked from commit 65cd4f6c99c1170bd0114dbd71b978012ea44d28)
Signed-off-by: Ajay Nandakumar <anandakumarm@nvidia.com>
Change-Id: I77dde73ba0c325c67275e72220419fd47faf4206
arch/arm/kernel/arch_timer.c
arch/arm64/Kconfig
arch/arm64/kernel/time.c
drivers/clocksource/arm_arch_timer.c