diff options
| author | Duncan Laurie <dlaurie@chromium.org> | 2014-09-06 06:53:12 -0700 |
|---|---|---|
| committer | chrome-internal-fetch <chrome-internal-fetch@google.com> | 2014-09-08 23:07:59 +0000 |
| commit | 724e361a4271fb9546c27755e123641a0b7aa2ae (patch) | |
| tree | 32c5402666e6e476e67e5874f20776467dc96a99 | |
| parent | 3e8a7187c81686c47b627eccc2c905b68b9589c3 (diff) | |
| download | chrome-ec-724e361a4271fb9546c27755e123641a0b7aa2ae.tar.gz | |
samus: Delay after asserting RTCRST
When RTCRST is asserted the PCH is not able to sequence properly
right away. In testing 5ms was usually suitable but to be safe a
10ms delay is added.
BUG=chrome-os-partner:31833
BRANCH=None
TEST=esc+refresh+power on samus EVT boots to recovery
Change-Id: I10045fe56e107e853ff297bd83ea5369c44a2020
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/216941
Reviewed-by: Alec Berg <alecaberg@chromium.org>
| -rw-r--r-- | board/samus/power_sequence.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/board/samus/power_sequence.c b/board/samus/power_sequence.c index b0c649f1d7..977d6a39c8 100644 --- a/board/samus/power_sequence.c +++ b/board/samus/power_sequence.c @@ -103,6 +103,7 @@ static void chipset_reset_rtc(void) gpio_set_level(GPIO_PCH_RTCRST_L, 0); udelay(100); gpio_set_level(GPIO_PCH_RTCRST_L, 1); + udelay(10 * MSEC); } } |