aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/rtc/rtc-mpc5121.c
diff options
context:
space:
mode:
authorJohn Stultz <john.stultz@linaro.org>2012-03-06 17:16:09 -0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-04-02 09:53:10 -0700
commit61d38cd909ad35ff497bf1a84cd57b2baf6d9c49 (patch)
tree6bc71ca944631479792cea4f1e1764523e308b00 /drivers/rtc/rtc-mpc5121.c
parentacff5ccd7dfccb0c28f367a2a684a7e8e3ee0112 (diff)
downloadkernel_samsung_smdk4412-61d38cd909ad35ff497bf1a84cd57b2baf6d9c49.zip
kernel_samsung_smdk4412-61d38cd909ad35ff497bf1a84cd57b2baf6d9c49.tar.gz
kernel_samsung_smdk4412-61d38cd909ad35ff497bf1a84cd57b2baf6d9c49.tar.bz2
rtc: Provide flag for rtc devices that don't support UIE
commit 4a649903f91232d02284d53724b0a45728111767 upstream. 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. Reported-by: Richard Weinberger <richard@nod.at> Tested-by: Richard Weinberger <richard@nod.at> Signed-off-by: John Stultz <john.stultz@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/rtc/rtc-mpc5121.c')
-rw-r--r--drivers/rtc/rtc-mpc5121.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/rtc/rtc-mpc5121.c b/drivers/rtc/rtc-mpc5121.c
index da60915..0fc2d22 100644
--- a/drivers/rtc/rtc-mpc5121.c
+++ b/drivers/rtc/rtc-mpc5121.c
@@ -360,6 +360,8 @@ static int __devinit mpc5121_rtc_probe(struct platform_device *op)
&mpc5200_rtc_ops, THIS_MODULE);
}
+ rtc->rtc->uie_unsupported = 1;
+
if (IS_ERR(rtc->rtc)) {
err = PTR_ERR(rtc->rtc);
goto out_free_irq;