d691045592
Zephyr's watchdog API is badly designed in the sense that it's a 1:1 abstraction on top of whatever Quark D2000 expects for its watchdog, instead of expecting a generic timeout value. This implementation tries as much as possible to calculate the watchdog timeout in a way that's compatible with a Quark D2000 running at 32MHz; a comment in adjust_timeout() explains this in more detail. Jira: ZEP-2296 Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
32 lines
482 B
Plaintext
32 lines
482 B
Plaintext
# Kconfig - Watchdog configuration options
|
|
#
|
|
#
|
|
# Copyright (c) 2015 Intel Corporation
|
|
#
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
#
|
|
|
|
#
|
|
# Watchdog options
|
|
#
|
|
menuconfig WATCHDOG
|
|
bool
|
|
prompt "Watchdog Support"
|
|
default n
|
|
help
|
|
Include support for watchdogs.
|
|
|
|
if WATCHDOG
|
|
|
|
source "drivers/watchdog/Kconfig.qmsi"
|
|
|
|
source "drivers/watchdog/Kconfig.stm32"
|
|
|
|
source "drivers/watchdog/Kconfig.cmsdk_apb"
|
|
|
|
source "drivers/watchdog/Kconfig.sam"
|
|
|
|
source "drivers/watchdog/Kconfig.esp32"
|
|
|
|
endif
|