summaryrefslogtreecommitdiff
path: root/src/mainboard/google/veyron_romy
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2015-07-16 17:55:54 -0500
committerPatrick Georgi <pgeorgi@google.com>2015-07-21 21:11:32 +0200
commite94c40b254a5019e7e25be4d2399ad31f30dd271 (patch)
treecc3f3e43e73ad9993526243befeef7d5f4a82188 /src/mainboard/google/veyron_romy
parenta3d36bd9693b78bc6ec2a30bef3413fa038d1a04 (diff)
skylake: take into account deep s3 in power failure check
If a resume from S3 is occuring one needs to take into account deep S3 in order to check the proper power failure bits. When deep S3 is enabled the suspend well will be turned off. Therefore don't look for that bit when determining a power failure. BUG=chrome-os-partner:42847 BRANCH=None TEST=Suspend and resumed with deep s3 enabled and disabled. Change-Id: I2b3372a40b3d8295ee881a283b31ca7704e6764a Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Original-Commit-Id: a3ba22be37d8700f4e8a4a0f5c05fb9290cfc9b2 Original-Change-Id: I890f71a7cbea65f1db942fe2229a220cf0e721b0 Original-Signed-off-by: Aaron Durbin <adurbin@chromium.org> Original-Reviewed-on: https://chromium-review.googlesource.com/286271 Original-Reviewed-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-on: http://review.coreboot.org/11007 Reviewed-by: Aaron Durbin <adurbin@chromium.org> Tested-by: build bot (Jenkins) Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Diffstat (limited to 'src/mainboard/google/veyron_romy')
0 files changed, 0 insertions, 0 deletions