summaryrefslogtreecommitdiffstats
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
committerJohn Stultz <john.stultz@linaro.org>2012-03-15 18:23:10 -0700
commit4a649903f91232d02284d53724b0a45728111767 (patch)
tree065a4aa03fc377d34f6b332fdb8b608c9bf0bc26 /drivers/rtc/rtc-mpc5121.c
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 '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 9d3cacc..613447a 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;
OpenPOWER on IntegriCloud