diff options
| author | Mulin Chao <mlchao@nuvoton.com> | 2021-04-07 19:31:03 -0700 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2021-04-14 22:15:45 +0000 |
| commit | 0e30757012ae4daaa97593a781f74d1bfd83e13d (patch) | |
| tree | 5f973ca4da6106f85a08f9f7f5c84e6df94d9a3e /zephyr/Kconfig | |
| parent | fd16f618fa1e34a8c007f6a66a1ff4c9e9ef0424 (diff) | |
| download | chrome-ec-0e30757012ae4daaa97593a781f74d1bfd83e13d.tar.gz | |
zephyr: Adjust watchdog warning timer value and delay time
Adjusts the watchdog warning timer value and its delay time definitions
to meet original chromium ec behavior. The system handles the warning
event at CONFIG_AUX_TIMER_PERIOD_MS & issues the watchdog reset event
at CONFIG_WATCHDOG_PERIOD_MS.
Zephyr NPCX watchdog provides a config WDT_NPCX_DELAY_CYCLES for
watchdog timeout delay. Set the zephyr timeout to
CONFIG_AUX_TIMER_PERIOD_MS as warning time. So the NPCX watchdog
hardware issue reset event at CONFIG_AUX_TIMER_PERIOD_MS +
WDT_NPCX_DELAY_CYCLES.
BUG=b:184683548
BRANCH=none
TEST=Build & boot ec on volteer.
TEST=
`waitms 1000` warning doesn't issue & ec doesn't reboot
`waitms 1200` warning issue & ec doesn't reboot
`waitms 1500` warning issue & ec doesn't reboot
`waitms 1700` warning issue & ec reboot
Cq-Depend: chromium:2813911
Signed-off-by: Mulin Chao <mlchao@nuvoton.com>
Signed-off-by: Wealian Liao <whliao@nuvoton.corp-partner.google.com>
Change-Id: Ibee9c18cd9d2bae6d34ee9366755dec99687c3d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2814728
Reviewed-by: Wai-Hong Tam <waihong@google.com>
Reviewed-by: Keith Short <keithshort@chromium.org>
Commit-Queue: Keith Short <keithshort@chromium.org>
Diffstat (limited to 'zephyr/Kconfig')
| -rw-r--r-- | zephyr/Kconfig | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/zephyr/Kconfig b/zephyr/Kconfig index 0b5f1dc100..e5b617d9c3 100644 --- a/zephyr/Kconfig +++ b/zephyr/Kconfig @@ -560,7 +560,7 @@ config PLATFORM_EC_VSTORE_SLOT_COUNT checking on resume. For this, one slot is enough. menuconfig PLATFORM_EC_WATCHDOG - bool "watchdog" + bool "Watchdog" depends on WATCHDOG default y help @@ -569,4 +569,11 @@ menuconfig PLATFORM_EC_WATCHDOG system) gets starved for CPU time and isn't able to fire its HOOK_TICK event. + Chromium EC system uses an auxiliary timer to handle the system + warning event. This leaves some time to the system for preparing & + printing the debug information. The interval between reloads of the + watchdog timer should be less than half of the auxiliary timer + (PLATFORM_EC_WATCHDOG_PERIOD_MS - + PLATFORM_EC_WATCHDOG_WARNING_LEADING_TIME_MS). + endif # PLATFORM_EC |