blob: bdaf5d4101d2e5c7c73581c3f759e7b0bc7ac86a [file] [log] [blame]
maxims@google.com0753bc22017-04-17 12:00:21 -07001menu "Watchdog Timer Support"
Ye Li253531b2017-02-22 16:21:48 +08002
Paolo Pisati45a6d232017-02-10 17:28:05 +01003config HW_WATCHDOG
4 bool
5
6config BCM2835_WDT
7 bool "Enable BCM2835/2836 watchdog driver"
8 select HW_WATCHDOG
9 help
10 Say Y here to enable the BCM2835/2836 watchdog
11
12 This provides basic infrastructure to support BCM2835/2836 watchdog
13 hardware, with a max timeout of ~15secs.
14
Ye Li253531b2017-02-22 16:21:48 +080015config ULP_WATCHDOG
16 bool "i.MX7ULP watchdog"
17 help
18 Say Y here to enable i.MX7ULP watchdog driver.
19
maxims@google.com0753bc22017-04-17 12:00:21 -070020config WDT
21 bool "Enable driver model for watchdog timer drivers"
22 depends on DM
23 help
24 Enable driver model for watchdog timer. At the moment the API
25 is very simple and only supports four operations:
26 start, restart, stop and reset (expire immediately).
27 What exactly happens when the timer expires is up to a particular
28 device/driver.
29
30config WDT_SANDBOX
31 bool "Enable Watchdog Timer support for Sandbox"
32 depends on SANDBOX && WDT
33 help
34 Enable Watchdog Timer support in Sandbox. This is a dummy device that
35 can be probed and supports all of the methods of WDT, but does not
36 really do anything.
37
maxims@google.com1eb0a462017-04-17 12:00:22 -070038config WDT_ASPEED
39 bool "Aspeed ast2400/ast2500 watchdog timer support"
40 depends on WDT
41 default y if ARCH_ASPEED
42 help
43 Select this to enable watchdog timer for Aspeed ast2500/ast2400 devices.
44 The watchdog timer is stopped when initialized. It performs reset, either
45 full SoC reset or CPU or just some peripherals, based on the flags.
46 It currently does not support Boot Flash Addressing Mode Detection or
47 Second Boot.
48
Ye Li253531b2017-02-22 16:21:48 +080049endmenu