tree 46c1842fc2a47aa4d7ee0c2c558f54bc50772b69
parent f1926ce63b996b42772b39e4b47bb4ef4ba748b4
author Thomas Gleixner <tglx@linutronix.de> 1221589970 -0700
committer Thomas Gleixner <tglx@linutronix.de> 1221598022 -0700

clockevents: make device shutdown robust

The device shut down does not cleanup the next_event variable of the
clock event device. So when the device is reactivated the possible
stale next_event value can prevent the device to be reprogrammed as it
claims to wait on a event already.

This is the root cause of the resurfacing suspend/resume problem,
where systems need key press to come back to life.

Fix this by setting next_event to KTIME_MAX when the device is shut
down. Use a separate function for shutdown which takes care of that
and only keep the direct set mode call in the broadcast code, where we
can not touch the next_event value.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>