summaryrefslogtreecommitdiff
path: root/board
diff options
context:
space:
mode:
authorDoug Anderson <dianders@chromium.org>2014-06-19 13:32:15 -0700
committerchrome-internal-fetch <chrome-internal-fetch@google.com>2014-06-23 21:48:42 +0000
commit68abc0f4288b6b9521f1dd05811f4b1f15e78287 (patch)
treed9152ce941dd0ba33fd67bd9e8d90d829679f684 /board
parent09db229f212a95bc674625895e68670a7aa57c00 (diff)
downloadchrome-ec-68abc0f4288b6b9521f1dd05811f4b1f15e78287.tar.gz
watchdog: Give more leeway to the independent watchdog
It would be really nice to be guaranteed to see watchdog warnings before we actually hit a watchdog reset even if something strange is going on with the CPU. Let's increase the margin between the timer and the independent so that the hardware watchdog is really hit as a last resort. It seems like a 1.6 second hardware watchdog wouldn't be the end of the world so let's bump that way rather than increasing the number of warnings. BRANCH=ToT BUG=chrome-os-partner:29162 TEST="waitms 1000" on EC console no longer ever reboots and "waitms 2000" usually does. Change-Id: Ic5e5ddec22fb8484cc7c552b19d3f2043c105d0c Signed-off-by: Doug Anderson <dianders@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/204895 Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'board')
-rw-r--r--board/zinger/board.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/board/zinger/board.h b/board/zinger/board.h
index d8184669c0..c0cc19f2d2 100644
--- a/board/zinger/board.h
+++ b/board/zinger/board.h
@@ -23,7 +23,7 @@
#define CONFIG_SHA1
#undef CONFIG_WATCHDOG_HELP
#undef CONFIG_WATCHDOG_PERIOD_MS
-#define CONFIG_WATCHDOG_PERIOD_MS 1800
+#define CONFIG_WATCHDOG_PERIOD_MS 2300
#undef CONFIG_LID_SWITCH
#undef CONFIG_TASK_PROFILING
#undef CONFIG_COMMON_GPIO