summaryrefslogtreecommitdiff
path: root/extra
diff options
context:
space:
mode:
authorWai-Hong Tam <waihong@google.com>2018-11-07 15:23:25 -0800
committerchrome-bot <chrome-bot@chromium.org>2018-12-06 22:06:39 -0800
commit0568b80369d39b9745099c143f168b941400a0b8 (patch)
tree09f9f5dcacdf05995d7c7439a6dcf80636682213 /extra
parent011a5575405bcc1f6f41e82eb5a896265b019467 (diff)
downloadchrome-ec-0568b80369d39b9745099c143f168b941400a0b8.tar.gz
cheza: Execute the power-off sequence on S3S5
Move the power-off call from S0S3 to S3S5, such that the hooks are triggered in an expected order. The console command apreset and apshutdown still have some wrong orders. Will be fixed later. BRANCH=none BUG=b:119050865 TEST=Tried the following cases: * Cold reset: $ dut-control cold_reset:on sleep:0.2 cold_reset:off Result: S3 -> S5S3 -> S3 -> S3S0 -> S0 * Long power press to shutdown: $ dut-control pwr_button:press sleep:20 pwr_button:release Result: S0 8s-> S0S3 -> S3 -> S3S5 12s-> S5 10s-> S5G3 -> G3 * Long power press to power-on but then shutdown: $ dut-control pwr_button:press sleep:20 pwr_button:release Result: G3 -> G3S5 -> S5 -> S5S3 8s-> S3S5 12s-> S5 10s-> S5G3 --> G3 * Not-long power press to power-on: $ dut-control pwr_button:press sleep:5 pwr_button:release Result: G3 -> G3S5 -> S5 -> S5S3 5s-> S3 -> S3S0 -> S0 TEST=Verified the suspend and shutdown hooks are triggered properly. Change-Id: I6350d1535f1c6374eacc710c1b3f0c6e25027d1f Signed-off-by: Wai-Hong Tam <waihong@google.com> Reviewed-on: https://chromium-review.googlesource.com/1325172 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Reviewed-by: Philip Chen <philipchen@chromium.org>
Diffstat (limited to 'extra')
0 files changed, 0 insertions, 0 deletions