diff options
| author | Daisuke Nojiri <dnojiri@chromium.org> | 2020-05-28 12:33:16 -0700 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2020-06-09 00:53:22 +0000 |
| commit | 84b959ca35604fe6d9d9d8e2b4088d1900f43ba0 (patch) | |
| tree | ec052679487286ae0b94098a639a07a841e4b558 /power/common.c | |
| parent | a46980b1865aeaed3d685e5ff2b14f790159894a (diff) | |
| download | chrome-ec-84b959ca35604fe6d9d9d8e2b4088d1900f43ba0.tar.gz | |
stoney: Initialize chipset state to S5 after sysjump
Currently, RW initializes the chipset state to G3 and forces the
chipset to shut down unless the AP is already powered on. This
behavior is based on the assumption that sysjump happens only upon
a request from the AP.
With EFS2, it's no longer the case because EC jumps while the AP
is off. AP may be off, resetting (i.e. s0->s5->s0), or shutting
down (s0->s5).
This patch makes RW set the chipset state to S5 if the corresponding
power signals are on.
BUG=b:156694627, b:157077589
BRANCH=none
TEST=test_that suite:faft_bios
Signed-off-by: Daisuke Nojiri <dnojiri@chromium.org>
Change-Id: Id8fdd10f411f403cb42bd8429fef737e88421ae9
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2220547
Reviewed-by: Aseda Aboagye <aaboagye@chromium.org>
Reviewed-by: Denis Brockus <dbrockus@chromium.org>
Diffstat (limited to 'power/common.c')
0 files changed, 0 insertions, 0 deletions