summaryrefslogtreecommitdiff
path: root/src/mainboard/amd/thatcher/Kconfig
diff options
context:
space:
mode:
authorStefan Reinauer <reinauer@chromium.org>2013-05-28 12:37:08 -0700
committerStefan Reinauer <stefan.reinauer@coreboot.org>2013-11-25 23:41:23 +0100
commit86ce7f92735d4e0a3c6938cf7695b2805f5f48b4 (patch)
tree4ea5c19dba176165f7bc8267510fb46a044903ba /src/mainboard/amd/thatcher/Kconfig
parent7ae7fc081b3832f1f6ba80eac8c92f788cbdd554 (diff)
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> 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> Reviewed-on: http://review.coreboot.org/4206 Tested-by: build bot (Jenkins) Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
Diffstat (limited to 'src/mainboard/amd/thatcher/Kconfig')
0 files changed, 0 insertions, 0 deletions