1menu "Watchdog Timer Support" 2 3config 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 15config ULP_WATCHDOG 16 bool "i.MX7ULP watchdog" 17 help 18 Say Y here to enable i.MX7ULP watchdog driver. 19 20config 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 38config 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 49endmenu 50