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-- | 2.9 KB |
| Kconfig.iosched | -rw-r--r-- | 1.9 KB |
| Makefile | -rw-r--r-- | 599 bytes |
| as-iosched.c | -rw-r--r-- | 38.5 KB |
| blk-barrier.c | -rw-r--r-- | 7.6 KB |
| blk-core.c | -rw-r--r-- | 54.0 KB |
| blk-exec.c | -rw-r--r-- | 2.6 KB |
| blk-integrity.c | -rw-r--r-- | 9.9 KB |
| blk-ioc.c | -rw-r--r-- | 4.0 KB |
| blk-map.c | -rw-r--r-- | 7.3 KB |
| blk-merge.c | -rw-r--r-- | 12.3 KB |
| blk-settings.c | -rw-r--r-- | 13.6 KB |
| blk-sysfs.c | -rw-r--r-- | 8.3 KB |
| blk-tag.c | -rw-r--r-- | 9.6 KB |
| blk.h | -rw-r--r-- | 1.9 KB |
| blktrace.c | -rw-r--r-- | 12.6 KB |
| bsg.c | -rw-r--r-- | 23.0 KB |
| cfq-iosched.c | -rw-r--r-- | 56.6 KB |
| cmd-filter.c | -rw-r--r-- | 5.5 KB |
| compat_ioctl.c | -rw-r--r-- | 21.9 KB |
| deadline-iosched.c | -rw-r--r-- | 11.5 KB |
| elevator.c | -rw-r--r-- | 26.3 KB |
| genhd.c | -rw-r--r-- | 19.5 KB |
| ioctl.c | -rw-r--r-- | 7.0 KB |
| noop-iosched.c | -rw-r--r-- | 2.6 KB |
| scsi_ioctl.c | -rw-r--r-- | 17.1 KB |
Computing file changes ...
