-
- Downloads
[PATCH] rtc framewok: rtc_wkalrm.enabled reporting updates
Fix a glitch in the procfs dumping of whether the alarm IRQ is enabled: use the traditional name (from drivers/char/rtc.c and many other places) of "alarm_IRQ", not "alrm_wakeup" (which didn't even match the efirtc code, which originated that reporting API). Also, update a few of the RTC drivers to stop providing that duplicate status, and/or to expose it properly when reporting the alarm state. We really don't want every RTC driver doing their own thing here... Signed-off-by:David Brownell <dbrownell@users.sourceforge.net> Acked-by:
Alessandro Zummo <a.zummo@towertech.it> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
Showing
- drivers/rtc/rtc-at91rm9200.c 3 additions, 2 deletionsdrivers/rtc/rtc-at91rm9200.c
- drivers/rtc/rtc-omap.c 1 addition, 2 deletionsdrivers/rtc/rtc-omap.c
- drivers/rtc/rtc-proc.c 1 addition, 1 deletiondrivers/rtc/rtc-proc.c
- drivers/rtc/rtc-s3c.c 2 additions, 4 deletionsdrivers/rtc/rtc-s3c.c
- drivers/rtc/rtc-sa1100.c 1 addition, 3 deletionsdrivers/rtc/rtc-sa1100.c
Loading
Please register or sign in to comment