Andrey Skvortsov 587c3f8ebe imx_watchdog: always set minimal timeout in reset_cpu ... The problem is that timeout bits in WCR register were leaved unchanged. So previously set timeout value was applied and therefore 'reset' command takes any value up to two minutes, depending on previous watchdog settings, instead of minimal 0.5 seconds. Signed-off-by: Andrey Skvortsov <andrej.skvortzov@gmail.com>		2016-01-07 17:54:53 +01:00
..
Kconfig	kconfig: add blank Kconfig files	2014-09-24 18:30:28 -04:00
Makefile	ls102xa: Fix reset hang	2015-10-12 12:56:32 -04:00
at91sam9_wdt.c	arm, at91, wdt: make timeout configurable	2015-02-07 23:43:20 +01:00
bfin_wdt.c	blackfin: Fix warning about undefined function	2014-07-07 19:47:09 -04:00
designware_wdt.c	watchdog/denali: Adding DesignWare watchdog driver support	2014-07-05 00:24:16 +02:00
ftwdt010_wdt.c	Add GPL-2.0+ SPDX-License-Identifier to source files	2013-07-24 09:44:38 -04:00
imx_watchdog.c	imx_watchdog: always set minimal timeout in reset_cpu	2016-01-07 17:54:53 +01:00
omap_wdt.c	arm, am335x: add watchdog support	2013-08-28 11:44:59 -04:00
s5p_wdt.c	Coding Style cleanup: remove trailing white space	2013-10-14 16:06:53 -04:00
xilinx_tb_wdt.c	microblaze: Fix watchdog initialization	2013-10-16 09:24:38 -04:00