summaryrefslogtreecommitdiffstats
path: root/include/linux/rtc.h
diff options
context:
space:
mode:
authorJohn Stultz <john.stultz@linaro.org>2012-03-06 17:16:09 -0800
committerJohn Stultz <john.stultz@linaro.org>2012-03-15 18:23:10 -0700
commit4a649903f91232d02284d53724b0a45728111767 (patch)
tree065a4aa03fc377d34f6b332fdb8b608c9bf0bc26 /include/linux/rtc.h
parent74a622be3db2898251cb524d1edbeaea589f2723 (diff)
downloadop-kernel-dev-4a649903f91232d02284d53724b0a45728111767.zip
op-kernel-dev-4a649903f91232d02284d53724b0a45728111767.tar.gz
rtc: Provide flag for rtc devices that don't support UIE
Richard Weinberger noticed that on some RTC hardware that doesn't support UIE mode, due to coarse granular alarms (like 1minute resolution), the current virtualized RTC support doesn't properly error out when UIE is enabled. Instead the current code queues an alarm for the next second, but it won't fire until up to a miniute later. This patch provides a generic way to flag this sort of hardware and fixes the issue on the mpc5121 where Richard noticed the problem. CC: stable@vger.kernel.org Reported-by: Richard Weinberger <richard@nod.at> Tested-by: Richard Weinberger <richard@nod.at> Signed-off-by: John Stultz <john.stultz@linaro.org>
Diffstat (limited to 'include/linux/rtc.h')
-rw-r--r--include/linux/rtc.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/include/linux/rtc.h b/include/linux/rtc.h
index 93f4d03..fcabfb4 100644
--- a/include/linux/rtc.h
+++ b/include/linux/rtc.h
@@ -202,7 +202,8 @@ struct rtc_device
struct hrtimer pie_timer; /* sub second exp, so needs hrtimer */
int pie_enabled;
struct work_struct irqwork;
-
+ /* Some hardware can't support UIE mode */
+ int uie_unsupported;
#ifdef CONFIG_RTC_INTF_DEV_UIE_EMUL
struct work_struct uie_task;
OpenPOWER on IntegriCloud