summaryrefslogtreecommitdiffstats
path: root/drivers/watchdog/imx_watchdog.c
Commit message (Collapse)AuthorAgeFilesLines
* watchdog/imx_watchdog: do not set WCR_WDWSebastian Siewior2015-03-251-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 initAnatolij Gustschin2013-10-311-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 watchdogTroy Kisky2013-01-131-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>
OpenPOWER on IntegriCloud