Thomas Gleixner 2344abbcbd 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>
2008-09-16 13:47:02 -07:00
..
2008-07-28 23:32:00 +02:00
2008-05-01 08:03:59 -07:00
2008-07-26 20:53:20 -04:00
2008-09-05 18:14:35 +02:00
2008-07-28 16:30:21 -07:00
2008-03-30 14:18:41 -07:00
2008-07-28 14:37:38 +02:00
2007-07-16 09:05:50 -07:00
2008-08-01 08:39:35 -05:00
2008-07-26 12:00:09 -07:00
2008-08-13 12:55:10 +02:00
2008-09-02 19:21:40 -07:00
2008-08-25 17:39:57 +02:00
2008-08-11 14:49:29 +02:00
2008-08-28 13:42:38 +02:00
2007-07-16 09:05:50 -07:00
2008-08-19 20:37:07 -07:00
2008-02-06 10:41:02 -08:00
2008-07-25 10:53:45 -07:00
2008-04-30 08:29:53 -07:00
2008-02-08 09:22:31 -08:00