summaryrefslogtreecommitdiff
path: root/util
diff options
context:
space:
mode:
authorNicolas Boichat <drinkcat@chromium.org>2018-10-22 16:56:10 +0800
committerchrome-bot <chrome-bot@chromium.org>2018-10-29 04:15:05 -0700
commit51a6070f845ed670c5a198a7045af3d3bb3bbdd4 (patch)
treea247c66e5299aae1d9a657fdd695c3759063ec40 /util
parent149190dd3a823d835be71ec4b4e4ae9e5120c774 (diff)
downloadchrome-ec-51a6070f845ed670c5a198a7045af3d3bb3bbdd4.tar.gz
system: Remember if reset was due to AP watchdog triggering
On MT8183, when EC detects a watchdog reset, EC needs to reboot itself in preparation for the next boot. This means that AP loses the reset cause (as AP system reset is toggled), and, therefore, we need to save the reset reason in the EC. BRANCH=none BUG=b:109900671 TEST=apshutdown, powerb, see that reset reason is: reset-pin TEST=Use test-wd from bug. Reset reason: reset-pin ap-watchdog Change-Id: I2e30306db5727a22de930f00dc30de40b9695bef Signed-off-by: Nicolas Boichat <drinkcat@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1295890 Reviewed-by: Jett Rink <jettrink@chromium.org>
Diffstat (limited to 'util')
-rw-r--r--util/ectool.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/util/ectool.c b/util/ectool.c
index bd7725131e..4cb4b71623 100644
--- a/util/ectool.c
+++ b/util/ectool.c
@@ -769,7 +769,8 @@ int cmd_uptimeinfo(int argc, char *argv[])
"usb-resume",
"rdd",
"rbox",
- "security"
+ "security",
+ "ap-watchdog"
};
struct ec_response_uptime_info r;