summaryrefslogtreecommitdiffstats
path: root/arch/x86/kernel/early-quirks.c
diff options
context:
space:
mode:
authorMark Langsdorf <mark.langsdorf@amd.com>2011-11-18 16:33:06 +0100
committerThomas Gleixner <tglx@linutronix.de>2011-12-08 21:47:22 +0100
commit2ded6e6a94c98ea453a156748cb7fabaf39a76b9 (patch)
tree0e9df0ea561e9e5aa64482f41407473b9ce34b4a /arch/x86/kernel/early-quirks.c
parent4e2b1c4f56227c742bbd2ea8e8f559567eb80c3f (diff)
downloadtalos-op-linux-2ded6e6a94c98ea453a156748cb7fabaf39a76b9.tar.gz
talos-op-linux-2ded6e6a94c98ea453a156748cb7fabaf39a76b9.zip
x86, hpet: Immediately disable HPET timer 1 if rtc irq is masked
When HPET is operating in RTC mode, the TN_ENABLE bit on timer1 controls whether the HPET or the RTC delivers interrupts to irq8. When the system goes into suspend, the RTC driver sends a signal to the HPET driver so that the HPET releases control of irq8, allowing the RTC to wake the system from suspend. The switchover is accomplished by a write to the HPET configuration registers which currently only occurs while servicing the HPET interrupt. On some systems, I have seen the system suspend before an HPET interrupt occurs, preventing the write to the HPET configuration register and leaving the HPET in control of the irq8. As the HPET is not active during suspend, it does not generate a wake signal and RTC alarms do not work. This patch forces the HPET driver to immediately transfer control of the irq8 channel to the RTC instead of waiting until the next interrupt event. Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com> Link: http://lkml.kernel.org/r/20111118153306.GB16319@alberich.amd.com Tested-by: Andreas Herrmann <andreas.herrmann3@amd.com> Signed-off-by: Andreas Herrmann <andreas.herrmann3@amd.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: stable@vger.kernel.org
Diffstat (limited to 'arch/x86/kernel/early-quirks.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud