summaryrefslogtreecommitdiff
path: root/common
diff options
context:
space:
mode:
authorBill Richardson <wfrichar@chromium.org>2016-03-30 12:26:01 -0700
committerchrome-bot <chrome-bot@chromium.org>2016-03-30 20:38:13 -0700
commit70378b86b4e5682b70a8145c9679e250280d6f14 (patch)
tree3dc7dbf91224facdeb36b6555028a78b2a59bc20 /common
parent55af6cc418c83c504f20145f075de645ff12aab6 (diff)
downloadchrome-ec-70378b86b4e5682b70a8145c9679e250280d6f14.tar.gz
Cr50: Include low-power exit triggers in reset causes
Some of the reset causes are found in another register when resuming from a low-power state. We know we'll need to distinguish among them eventually, so we might as well decode them now. BUG=chrome-os-partner:49955 BRANCH=none TEST=make buildall; test on Cr50 I forced the system into deep sleep and observed that the reset cause is accurately recorded on resume. Doing that requires a fair amount of hacks and manual effort, and can't happen by accident. Future CLs will make use of this. The current, normal behavior is completely unaffected. Change-Id: I5a7b19dee8bff1ff1703fbbcc84cff4e374cf872 Signed-off-by: Bill Richardson <wfrichar@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/336314 Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'common')
-rw-r--r--common/system.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/common/system.c b/common/system.c
index afa278884d..7c3117a292 100644
--- a/common/system.c
+++ b/common/system.c
@@ -84,7 +84,7 @@ static struct jump_data *jdata;
static const char * const reset_flag_descs[] = {
"other", "reset-pin", "brownout", "power-on", "watchdog", "soft",
"hibernate", "rtc-alarm", "wake-pin", "low-battery", "sysjump",
- "hard", "ap-off", "preserved"};
+ "hard", "ap-off", "preserved", "usb-resume"};
static uint32_t reset_flags;
static int jumped_to_image;