summaryrefslogtreecommitdiff
path: root/board/nocturne_fp/OWNERS
diff options
context:
space:
mode:
authorWai-Hong Tam <waihong@google.com>2020-06-17 14:58:27 -0700
committerCommit Bot <commit-bot@chromium.org>2020-06-18 05:19:07 +0000
commit3bb7d7b0e62a5845ba137446b4083c32a83240c9 (patch)
treefabdedaba68769af8daa61c15a4f01ae6b09db62 /board/nocturne_fp/OWNERS
parent9397f9357992b8719eb42054d0bf1e75a96cfd12 (diff)
downloadchrome-ec-3bb7d7b0e62a5845ba137446b4083c32a83240c9.tar.gz
sc7180: Handle the exception cases of power on
Make the switchcap and PMIC functions return a success or error code. In the power on sequence, an error happening in the middle will make it skip the remaining steps, and then calls the power off sequence to restore back S5. The power off sequence don't care about any error and perform the entire procedure. BRANCH=None BUG=b:159101052 TEST=Manually trigger power on and power off. TEST=Forced to a switchcap error, it went back to S5. > gpioset DA9313_GPIO0 0 > power on Requesting power on > RTC: 0x5ed1d4a7 (1590809767.00 s) [7177.018477 power state 4 = G3->S5, in 0x0005] RTC: 0x5ed1d4a7 (1590809767.00 s) [7177.019409 power state 1 = S5, in 0x0005] [7177.019918 power on 4] RTC: 0x5ed1d4a7 (1590809767.00 s) [7177.021168 power state 5 = S5->S3, in 0x0005] [7177.021700 power button released in time] [7177.024143 set_system_power(1)] [7177.076708 SWITCHCAP NO POWER GOOD!] [7177.187407 set_system_power(0)] RTC: 0x5ed1d4a7 (1590809767.00 s) [7177.188564 power state 1 = S5, in 0x0005] Change-Id: Iaf2676d84513056b3a1deb4f4c554c607e588c37 Signed-off-by: Wai-Hong Tam <waihong@google.com> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2250668 Reviewed-by: Alexandru M Stan <amstan@chromium.org> Reviewed-by: Stephen Boyd <swboyd@chromium.org>
Diffstat (limited to 'board/nocturne_fp/OWNERS')
0 files changed, 0 insertions, 0 deletions