summaryrefslogtreecommitdiffstats
path: root/drivers/rtc/rtc-m41t80.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2011-12-09 09:39:15 +1100
committerJohn Stultz <john.stultz@linaro.org>2011-12-13 12:26:11 -0800
commit93b2ec0128c431148b216b8f7337c1a52131ef03 (patch)
tree0782370c8c04c182e67b26414e3d4180616db94b /drivers/rtc/rtc-m41t80.c
parentc9c024b3f3e07d087974db4c0dc46217fff3a6c0 (diff)
downloadlinux-93b2ec0128c431148b216b8f7337c1a52131ef03.tar.gz
linux-93b2ec0128c431148b216b8f7337c1a52131ef03.tar.bz2
linux-93b2ec0128c431148b216b8f7337c1a52131ef03.zip
rtc: Expire alarms after the time is set.
If the alarm time programming in the rtc is ever in the past, it won't fire, and any other alarm will be queued after it so they won't fire either. So any time that the alarm might be in the past, we need to trigger the irq handler to ensure the old alarm is cleared and the timer queue is fully in the future. This can happen: - when we first initialise the alarm - when we set the time in the rtc. so follow both of these by scheduling the timer work function. CC: stable@kernel.org Signed-off-by: NeilBrown <neilb@suse.de> [Also catch set_mmss case -jstultz] Signed-off-by: John Stultz <john.stultz@linaro.org>
Diffstat (limited to 'drivers/rtc/rtc-m41t80.c')
0 files changed, 0 insertions, 0 deletions