1Watchdog driver general info 2 3CONFIG_HW_WATCHDOG 4 This enables hw_watchdog_reset to be called during various loops, 5 including waiting for a character on a serial port. But it 6 does not also call hw_watchdog_init. Boards which want this 7 enabled must call this function in their board file. This split 8 is useful because some rom's enable the watchdog when downloading 9 new code, so it must be serviced, but the board would rather it 10 was off. And, it cannot always be turned off once on. 11 12CONFIG_WATCHDOG_TIMEOUT_MSECS 13 Can be used to change the timeout for i.mx31/35/5x/6x. 14 If not given, will default to maximum timeout. This would 15 be 128000 msec for i.mx31/35/5x/6x. 16 17CONFIG_WDT_AT91 18 Available for AT91SAM9 to service the watchdog. 19 20CONFIG_FTWDT010_WATCHDOG 21 Available for FTWDT010 to service the watchdog. 22 23CONFIG_FTWDT010_HW_TIMEOUT 24 Can be used to change the timeout for FTWDT010. 25 26CONFIG_IMX_WATCHDOG 27 Available for i.mx31/35/5x/6x to service the watchdog. This is not 28 automatically set because some boards (vision2) still need to define 29 their own hw_watchdog_reset routine. 30 TODO: vision2 is removed now, so perhaps this can be changed. 31 32CONFIG_XILINX_TB_WATCHDOG 33 Available for Xilinx Axi platforms to service timebase watchdog timer. 34