Vic (Chun-Ju) Yang dc82ca44d3 mec1322: Refine reset cause detection ...

The VBAT POR indication is unreliable for detecting a power-on reset,
and thus we often see "unknown" reset cause when we should see
"power-on". A better indication is to check for VCC1 POR, which
manifests by clearing watchdog count. The catch is that we still cannot
tell power-on reset from reset-pin reset.

Also, to distinguish soft/hard reset from actual watchdog reset, we need
to explicitly save soft/hard reset flag before triggering watchdog
reset.

BUG=chrome-os-partner:24107
TEST=Power cycle EVB and see 'power-on' reset cause.
TEST='reboot' and see 'soft' reset cause.
TEST='reboot hard' and see 'hard' reset cause.
TEST='waitms 2000' and see 'watchdog' reset cause.
BRANCH=None

Change-Id: I0075f5bf5cdb032d206c4a53c586b75b69093235
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/182120
Reviewed-by: Randall Spangler <rspangler@chromium.org>

2014-01-11 04:46:46 +00:00

..

host

Remove old TODO comment in emulator UART module

2014-01-09 05:30:42 +00:00

it83xx

ite: WORKAROUND reduce data SRAM to 8kB

2014-01-08 14:18:19 +00:00

lm4

Add squawks board

2014-01-08 02:22:34 +00:00

mec1322

mec1322: Refine reset cause detection

2014-01-11 04:46:46 +00:00

stm32

Convert vboot hash calculation from task to deferred function

2014-01-09 20:25:11 +00:00