Searched hist:"2344 abbc" (Results 1 – 4 of 4) sorted by relevance
/openbmc/linux/kernel/time/ |
H A D | tick-internal.h | 2344abbc Tue Sep 16 13:32:50 CDT 2008 Thomas Gleixner <tglx@linutronix.de> 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> 2344abbc Tue Sep 16 13:32:50 CDT 2008 Thomas Gleixner <tglx@linutronix.de> 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>
|
H A D | clockevents.c | 2344abbc Tue Sep 16 13:32:50 CDT 2008 Thomas Gleixner <tglx@linutronix.de> 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> 2344abbc Tue Sep 16 13:32:50 CDT 2008 Thomas Gleixner <tglx@linutronix.de> 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>
|
H A D | tick-common.c | 2344abbc Tue Sep 16 13:32:50 CDT 2008 Thomas Gleixner <tglx@linutronix.de> 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> 2344abbc Tue Sep 16 13:32:50 CDT 2008 Thomas Gleixner <tglx@linutronix.de> 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>
|
H A D | tick-broadcast.c | 2344abbc Tue Sep 16 13:32:50 CDT 2008 Thomas Gleixner <tglx@linutronix.de> 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> 2344abbc Tue Sep 16 13:32:50 CDT 2008 Thomas Gleixner <tglx@linutronix.de> 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>
|