summaryrefslogtreecommitdiffstats
path: root/drivers/rtc/rtc-pl031.c
diff options
context:
space:
mode:
authorLaxman Dewangan2013-02-22 01:44:38 +0100
committerLinus Torvalds2013-02-22 02:22:28 +0100
commit225ccc28726ca8849e5bfc9148c343e258737f3b (patch)
tree4efbacf2f97d59f10cd5a608fea77fca5fce1b6c /drivers/rtc/rtc-pl031.c
parentdrivers/rtc/rtc-tps65910.c: use sleep_pm_ops macro for initialising suspend/r... (diff)
downloadkernel-qcow2-linux-225ccc28726ca8849e5bfc9148c343e258737f3b.tar.gz
kernel-qcow2-linux-225ccc28726ca8849e5bfc9148c343e258737f3b.tar.xz
kernel-qcow2-linux-225ccc28726ca8849e5bfc9148c343e258737f3b.zip
drivers/rtc/rtc-tps65910.c: set irq flag to IRQF_EARLY_RESUME during irq request
All interrupt get disabled during system suspend and enabled during system resume. The enabling/disabling of interrupt happen in sequence of interrupt registration with framework. Therefore, in resume, the parent interrupt of this device enabled before the RTC irq interrupt enabled. If RTC is enabled for alarm wake and if system wake by alarm then there is interrupt pending for RTC. In resume, the parent interrupt get enabled before the rtc interrupt and hence ISR get served. In ISR, it founds that rtc interrupt is disabled and so it does not call the rtc isr handler and hence it misses the interrupt. Setting flag for early resume so that rtc interrupt get enabled before parent interrupt and so rtc interrupt get enabled when parent interrupt handler check for interrupt of device and call the rtc handler if it is there. This way it will not miss the interrupt. Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com> Cc: Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/rtc/rtc-pl031.c')
0 files changed, 0 insertions, 0 deletions