clockevents: Make suspend/resume calls explicit
authorThomas Gleixner <tglx@linutronix.de>
Wed, 25 Mar 2015 12:09:16 +0000 (13:09 +0100)
committerIngo Molnar <mingo@kernel.org>
Wed, 1 Apr 2015 12:22:59 +0000 (14:22 +0200)
commit4ffee521f36390c7720d493591b764ca35c8030b
tree9836af97487f83a0680c293f187cd116875ec2c5
parentdb6f672ef11d7a3c5aa128a3c3e57c92580a25f7
clockevents: Make suspend/resume calls explicit

clockevents_notify() is a leftover from the early design of the
clockevents facility. It's really not a notification mechanism,
it's a multiplex call.

We are way better off to have explicit calls instead of this
monstrosity. Split out the suspend/resume() calls and invoke
them directly from the call sites.

No locking required at this point because these calls happen
with interrupts disabled and a single cpu online.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
[ Rebased on top of 4.0-rc5. ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/713674030.jVm1qaHuPf@vostro.rjw.lan
[ Rebased on top of latest timers/core. ]
Signed-off-by: Ingo Molnar <mingo@kernel.org>
arch/x86/xen/suspend.c
include/linux/clockchips.h
include/linux/tick.h
kernel/time/clockevents.c
kernel/time/tick-common.c
kernel/time/tick-internal.h
kernel/time/timekeeping.c