diff options
| author | Ard Biesheuvel <ard.biesheuvel@linaro.org> | 2015-01-13 12:28:53 +0000 |
|---|---|---|
| committer | Matt Fleming <matt.fleming@intel.com> | 2015-01-20 15:46:21 +0000 |
| commit | 822a0279287603f150b991d0ea319bbba5aa235a (patch) | |
| tree | 0c4ad7af0bb16c41c07af6ef1fbcb324213b4a5f /drivers/rtc | |
| parent | ddeeefe2dfbe1fa6b116b9362b1bec465b64c873 (diff) | |
| download | linux-822a0279287603f150b991d0ea319bbba5aa235a.tar.gz linux-822a0279287603f150b991d0ea319bbba5aa235a.tar.bz2 linux-822a0279287603f150b991d0ea319bbba5aa235a.zip | |
efi: rtc-efi: Mark UIE as unsupported
Tools like hwclock attempt to enable the RTC update interrupt (UIE) to
maximize the accuracy of the reported time value. The EFI rtc does not
have interrupt capability so this is a pointless exercise to begin with,
but the generic RTC framework ends up issuing a SetWakeupTime() Runtime
Services call before drawing that conclusion on its own.
Instead, we can mark UIE as unsupported at driver probe time. The net
result is the same, but without the spurious SetWakeupTime() call.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
Diffstat (limited to 'drivers/rtc')
| -rw-r--r-- | drivers/rtc/rtc-efi.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/rtc/rtc-efi.c b/drivers/rtc/rtc-efi.c index 53b589dc34eb..d30fb65fbffa 100644 --- a/drivers/rtc/rtc-efi.c +++ b/drivers/rtc/rtc-efi.c @@ -218,6 +218,7 @@ static int __init efi_rtc_probe(struct platform_device *dev) if (IS_ERR(rtc)) return PTR_ERR(rtc); + rtc->uie_unsupported = 1; platform_set_drvdata(dev, rtc); return 0; |