diff options
| author | Thomas Gleixner <[email protected]> | 2008-09-16 18:32:50 +0000 |
|---|---|---|
| committer | Thomas Gleixner <[email protected]> | 2008-09-16 20:47:02 +0000 |
| commit | 2344abbcbdb82140050e8be29d3d55e4f6fe860b (patch) | |
| tree | 46c1842fc2a47aa4d7ee0c2c558f54bc50772b69 /lib/bitmap.c | |
| parent | clocksource, acpi_pm.c: fix check for monotonicity (diff) | |
| download | kernel-2344abbcbdb82140050e8be29d3d55e4f6fe860b.tar.gz kernel-2344abbcbdb82140050e8be29d3d55e4f6fe860b.zip | |
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 <[email protected]>
Diffstat (limited to 'lib/bitmap.c')
0 files changed, 0 insertions, 0 deletions