Commit message (Collapse) | Author | Age | Lines | |
---|---|---|---|---|
* | watchdog/imx_watchdog: do not set WCR_WDW | Sebastian Siewior | 2015-03-25 | -2/+1 |
| | | | | | | | | | | | | | | with WCR_WDW set, the watchdog won't trigger if we bootet linux and idle around while the watchdog is not triggered. It seems the timer makes progress very slowly if at all. I managed to remain 20minutes alive while the timeout was set to 60secs. It reboots within 60secs if I start a busyloop in userland (something like "while (1) { }"). While I don't see a reason why the WDT should not be running while the CPU is in idle, I'm dropping this bit. Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de> Acked-by: Stefano Babic <sbabic@denx.de> | |||
* | imx_watchdog: do not soft-reset while watchdog init | Anatolij Gustschin | 2013-10-31 | -1/+2 |
| | | | | | | | | Currently the driver clears WCR_SRS bit when enabling the watchdog and this causes a software reset. Do not clear WCR_SRS. Signed-off-by: Anatolij Gustschin <agust@denx.de> | |||
* | mx31/mx35/mx51/mx53/mx6: add watchdog | Troy Kisky | 2013-01-13 | -0/+66 |
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> |