summaryrefslogtreecommitdiff
path: root/src/mainboard/bcom
diff options
context:
space:
mode:
authorDuncan Laurie <dlaurie@chromium.org>2017-03-07 19:22:24 -0800
committerDuncan Laurie <dlaurie@chromium.org>2017-03-08 19:08:09 +0100
commitac2cbd0ffbcf4950c899ea8336fd6fbb8833569b (patch)
tree16d7e4ea5d91d8508c42bdfc4a92f62033788aff /src/mainboard/bcom
parentcb76d50f0d15eada406e51a096d78553e3d4184e (diff)
intel/skylake: Filter suspend well power failure event for Deep Sx
If Deep Sx is enabled the event log will get entries added on every power sequence transition indicating that the suspend well has failed. When a board is using Deep Sx by design this is intended behavior and just fills the logs with extraneous events. To make this work the device init state has to be executed first so it actually enables the Deep Sx policies in the SOC since this code does not have any hooks back into the devicetree to read the intended setting from there. BUG=b:36042662 BRANCH=none TEST=Perform suspend/resume on Eve device with Deep S3 enabled, and then check the event log to be sure that it does not contain the "SUS Power Fail" event. Change-Id: I3c8242baa63685232025e1dfef5595ec0ec6d14a Signed-off-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-on: https://review.coreboot.org/18664 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/bcom')
0 files changed, 0 insertions, 0 deletions