summaryrefslogtreecommitdiff
path: root/fs/efs
diff options
context:
space:
mode:
authorzhuo-hao <zhuo-hao.lee@intel.com>2015-11-17 12:08:07 (GMT)
committerJohn Stultz <john.stultz@linaro.org>2015-12-04 06:31:42 (GMT)
commita0e3213f836640065e2a23ad55fa6f72e812a4f1 (patch)
tree4e88e156fa80aebe9bead07c24816911462814de /fs/efs
parent34db37c63a08b8f06f8ff15c5c301a26635ddf25 (diff)
downloadlinux-a0e3213f836640065e2a23ad55fa6f72e812a4f1.tar.xz
alarmtimer: Avoid unexpected rtc interrupt when system resume from S3
Before the system go to suspend (S3), if user create a timer with clockid CLOCK_REALTIME_ALARM/CLOCK_BOOTTIME_ALARM and set a "large" timeout value to this timer. The function alarmtimer_suspend will be called to setup a timeout value to RTC timer to avoid the system sleep over time. However, if the system wakeup early than RTC timeout, the RTC timer will not be cleared. And this will cause the hpet_rtc_interrupt come unexpectedly until the RTC timeout. To fix this problem, just adding alarmtimer_resume to cancel the RTC timer. This was noticed because the HPET RTC emulation fires an interrupt every 16ms(=1/2^DEFAULT_RTC_SHIFT) up to the point where the alarm time is reached. This program always hits this situation (https://lkml.org/lkml/2015/11/8/326), if system wake up earlier than alarm time. Cc: Thomas Gleixner <tglx@linutronix.de> Cc: John Stultz <john.stultz@linaro.org> Signed-off-by: Zhuo-hao Lee <zhuo-hao.lee@intel.com> [jstultz: Tweak commit subject & formatting slightly] Signed-off-by: John Stultz <john.stultz@linaro.org>
Diffstat (limited to 'fs/efs')
0 files changed, 0 insertions, 0 deletions