| Troy Kisky | abbab70 | 2012-10-22 15:19:01 +0000 | [diff] [blame] | 1 | Watchdog driver general info |
| 2 | |
| 3 | CONFIG_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 | |
| 12 | CONFIG_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 | |
| 17 | CONFIG_AT91SAM9_WATCHDOG |
| 18 | Available for AT91SAM9 to service the watchdog. |
| 19 | |
| 20 | CONFIG_FTWDT010_WATCHDOG |
| 21 | Available for FTWDT010 to service the watchdog. |
| 22 | |
| 23 | CONFIG_FTWDT010_HW_TIMEOUT |
| 24 | Can be used to change the timeout for FTWDT010. |
| 25 | |
| 26 | CONFIG_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. |
| Michal Simek | 0f21f98 | 2013-04-22 11:23:16 +0200 | [diff] [blame] | 30 | |
| 31 | CONFIG_XILINX_TB_WATCHDOG |
| 32 | Available for Xilinx Axi platforms to service timebase watchdog timer. |
| Sonic Zhang | e9a389a | 2013-04-07 18:02:37 +0800 | [diff] [blame] | 33 | |
| 34 | CONFIG_BFIN_WATCHDOG |
| 35 | Available for bf5xx and bf6xx to service the watchdog. |