Revision 2344abbcbdb82140050e8be29d3d55e4f6fe860b authored by Thomas Gleixner on 16 September 2008, 18:32:50 UTC, committed by Thomas Gleixner on 16 September 2008, 20:47:02 UTC
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>
1 parent f1926ce
| File | Mode | Size |
|---|---|---|
| Kconfig | -rw-r--r-- | 7.7 KB |
| Makefile | -rw-r--r-- | 237 bytes |
| console.c | -rw-r--r-- | 1.8 KB |
| disk.c | -rw-r--r-- | 20.3 KB |
| main.c | -rw-r--r-- | 16.1 KB |
| power.h | -rw-r--r-- | 6.4 KB |
| poweroff.c | -rw-r--r-- | 1000 bytes |
| process.c | -rw-r--r-- | 6.1 KB |
| snapshot.c | -rw-r--r-- | 49.9 KB |
| swap.c | -rw-r--r-- | 14.6 KB |
| swsusp.c | -rw-r--r-- | 6.5 KB |
| user.c | -rw-r--r-- | 9.3 KB |
Computing file changes ...
