diff options
| author | Troy Kisky <troy.kisky@boundarydevices.com> | 2012-10-22 15:19:01 +0000 |
|---|---|---|
| committer | Stefano Babic <sbabic@denx.de> | 2013-01-13 11:39:57 +0100 |
| commit | abbab70363dcdb270cbf24d47849214dd3a3e010 (patch) | |
| tree | 2eb6f30be46ddc350e5635179dabdd126be2b0cd /doc | |
| parent | 17c5ef20073c49ae1a10150b4194b25b6f1154fe (diff) | |
mx31/mx35/mx51/mx53/mx6: add watchdog
Use a common watchdog driver for all these cpus.
Signed-off-by: Troy Kisky <troy.kisky@boundarydevices.com>
Acked-by: Stefano Babic <sbabic@denx.de>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/README.watchdog | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/doc/README.watchdog b/doc/README.watchdog new file mode 100644 index 00000000000..ee65008b4be --- /dev/null +++ b/doc/README.watchdog @@ -0,0 +1,29 @@ +Watchdog driver general info + +CONFIG_HW_WATCHDOG + This enables hw_watchdog_reset to be called during various loops, + including waiting for a character on a serial port. But it + does not also call hw_watchdog_init. Boards which want this + enabled must call this function in their board file. This split + is useful because some rom's enable the watchdog when downloading + new code, so it must be serviced, but the board would rather it + was off. And, it cannot always be turned off once on. + +CONFIG_WATCHDOG_TIMEOUT_MSECS + Can be used to change the timeout for i.mx31/35/5x/6x. + If not given, will default to maximum timeout. This would + be 128000 msec for i.mx31/35/5x/6x. + +CONFIG_AT91SAM9_WATCHDOG + Available for AT91SAM9 to service the watchdog. + +CONFIG_FTWDT010_WATCHDOG + Available for FTWDT010 to service the watchdog. + +CONFIG_FTWDT010_HW_TIMEOUT + Can be used to change the timeout for FTWDT010. + +CONFIG_IMX_WATCHDOG + Available for i.mx31/35/5x/6x to service the watchdog. This is not + automatically set because some boards (vision2) still need to define + their own hw_watchdog_reset routine. |