RTC: Skip rtc_init() in S3 resume path

In addition to not clearing the pending interrupts, we also
don't want to reset the RTC control register when booting
with an S3 resume.

On most new systems, when the RTC well is losing power, we
will also lose state that is required to perform a resume,
so we end up in a normal boot anyways. Hence don't do any
RTC initialization in the S3 resume path.

Signed-off-by: Stefan Reinauer <reinauer@google.com>
BUG=none
TEST=Resume on Link, observe RTC initialization is skipped
BRANCH=none

Change-Id: I73b486082faa741e9dccd15f2b8e3a8399c98f80
Reviewed-on: https://gerrit.chromium.org/gerrit/56826
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-by: Derek Basehore <dbasehore@chromium.org>
Commit-Queue: Stefan Reinauer <reinauer@google.com>
Tested-by: Stefan Reinauer <reinauer@google.com>
This commit is contained in:
Stefan Reinauer 2013-05-28 12:37:08 -07:00 committed by ChromeBot
commit 887edac45c

View file

@ -71,6 +71,16 @@ void rtc_init(int invalid)
unsigned char x;
#endif
#if CONFIG_HAVE_ACPI_RESUME
/* Avoid clearing pending interrupts and resetting the RTC control
* register in the resume path because the Linux kernel relies on
* this to know if it should restart the RTC timerqueue if the wake
* was due to the RTC alarm.
*/
if (acpi_slp_type == 3)
return;
#endif
printk(BIOS_DEBUG, "RTC Init\n");
#if CONFIG_USE_OPTION_TABLE
@ -128,16 +138,6 @@ void rtc_init(int invalid)
PC_CKS_RANGE_END,PC_CKS_LOC);
#endif
#if CONFIG_HAVE_ACPI_RESUME
/*
* Avoid clearing pending interrupts in the resume path because
* the Linux kernel relies on this to know if it should restart
* the RTC timerqueue if the wake was due to the RTC alarm.
*/
if (acpi_slp_type == 3)
return;
#endif
/* Clear any pending interrupts */
(void) cmos_read(RTC_INTR_FLAGS);
}