summaryrefslogtreecommitdiff
path: root/.gitignore
diff options
context:
space:
mode:
authorDuncan Laurie <dlaurie@chromium.org>2012-09-05 10:52:44 -0700
committerStefan Reinauer <stefan.reinauer@coreboot.org>2012-11-08 19:40:05 +0100
commit4b1610d766aa1ea0c825b39600fe8a3eb6d2a6be (patch)
tree27558918e6f4afd915ae7273d03b99de0cc58ff9 /.gitignore
parent2558c736a06c416e41bb35c2e6439f457e541f61 (diff)
downloadcoreboot-4b1610d766aa1ea0c825b39600fe8a3eb6d2a6be.tar.xz
RTC: Don't clear pending interrupt in resume path
The linux kernel relies on the RTC reporting pending interrupts if the RTC alarm was used to wake the system. If we clear these flags here then the rtc-cmos driver in the kernel will think that no interrupts are pending and will not re-start the timerqueue to handle the alarm timerqueue node. This flag doesn't exist in SMM but the rtc code is compiled there. Since rtc_init() is not called by SMM it is guarded with an ifdef. I performed several thousand suspend/resume cycles without seeing an issue where hwclock was unable to read from /dev/rtc. There still is a potential kernel issue where the timerqueue can stall but this makes that much less likely to happen on resume. Change-Id: I5a343da4ce5c4c8ec4783b4e503869ccfa5077f0 Signed-off-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-on: http://review.coreboot.org/1741 Tested-by: build bot (Jenkins) Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions