blob: 2034e3c620f8d06859e5e88acfff1d32eef8af88 [file] [log] [blame]
maxims@google.com0753bc22017-04-17 12:00:21 -07001menu "Watchdog Timer Support"
Ye Li253531b2017-02-22 16:21:48 +08002
3config ULP_WATCHDOG
4 bool "i.MX7ULP watchdog"
5 help
6 Say Y here to enable i.MX7ULP watchdog driver.
7
maxims@google.com0753bc22017-04-17 12:00:21 -07008config WDT
9 bool "Enable driver model for watchdog timer drivers"
10 depends on DM
11 help
12 Enable driver model for watchdog timer. At the moment the API
13 is very simple and only supports four operations:
14 start, restart, stop and reset (expire immediately).
15 What exactly happens when the timer expires is up to a particular
16 device/driver.
17
18config WDT_SANDBOX
19 bool "Enable Watchdog Timer support for Sandbox"
20 depends on SANDBOX && WDT
21 help
22 Enable Watchdog Timer support in Sandbox. This is a dummy device that
23 can be probed and supports all of the methods of WDT, but does not
24 really do anything.
25
maxims@google.com1eb0a462017-04-17 12:00:22 -070026config WDT_ASPEED
27 bool "Aspeed ast2400/ast2500 watchdog timer support"
28 depends on WDT
29 default y if ARCH_ASPEED
30 help
31 Select this to enable watchdog timer for Aspeed ast2500/ast2400 devices.
32 The watchdog timer is stopped when initialized. It performs reset, either
33 full SoC reset or CPU or just some peripherals, based on the flags.
34 It currently does not support Boot Flash Addressing Mode Detection or
35 Second Boot.
36
Ye Li253531b2017-02-22 16:21:48 +080037endmenu