summaryrefslogtreecommitdiff
path: root/payloads/linuxcheck
diff options
context:
space:
mode:
authorSubrata Banik <subratabanik@google.com>2023-01-16 15:22:07 +0530
committerSubrata Banik <subratabanik@google.com>2023-01-18 11:49:59 +0000
commitb03d6f15b48468c6f3a5da45df6204eb43db6eaa (patch)
treec58c5c03b4f9625256d49c8b1ae8ffda581e2e68 /payloads/linuxcheck
parent6d64155cc8eb03912e500fee5631156bf70e7ace (diff)
soc/intel/meteorlake: Fix incorrect `prev_sleep_state` issue
The patch fixes indication of incorrect `prev_sleep_state` on the next boot after global reset trigger. The existing code misses an important check about `if PCH doesn't set the WAK_STS` while checking power failure. As a result, every early warm/global reset is considered as power failure after looking into the PMC MMIO CON-A register alone (as ignoring the ACPI PM_CTRL.WAK_STS bit). As per the code comment this code logic is expected to check the power failure reason if PCH doesn't set the WAK_STS while waking from G3 state. TEST=Able to build and boot google/rex. Without this patch: Observation: Resuming after a warm reset is considered as `prev_sleep_state 5` although the SLP_TYP is zero and WAK_STS bit is set. pm1_sts: 8100 pm1_en: 0000 pm1_cnt: 00000000 GEN_PMCON: d1215238 00002200 .... prev_sleep_state 5 With this patch: Observation: Resuming after a warm reset is considered as `prev_sleep_state 0`. It matches with the SLP_TYP is zero and WAK_STS bit is set. pm1_sts: 8100 pm1_en: 0000 pm1_cnt: 00000000 GEN_PMCON: d1215238 00002200 .... prev_sleep_state 0 Signed-off-by: Subrata Banik <subratabanik@google.com> Change-Id: Idc40045445cccc5b34fb49901d9ef548f2f0560b Reviewed-on: https://review.coreboot.org/c/coreboot/+/71986 Reviewed-by: Lean Sheng Tan <sheng.tan@9elements.com> Reviewed-by: Sridhar Siricilla <sridhar.siricilla@intel.com> Reviewed-by: Kapil Porwal <kapilporwal@google.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'payloads/linuxcheck')
0 files changed, 0 insertions, 0 deletions