summaryrefslogtreecommitdiff
path: root/drivers/watchdog/octeon-wdt-nmi.S
diff options
context:
space:
mode:
authorOleksij Rempel <o.rempel@pengutronix.de>2017-09-26 08:11:22 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-04-12 12:32:13 +0200
commit1cf98fd005f54f480aba21f1d73a0059f460a353 (patch)
tree775eea00d0e2c472700b4bbdff147c05034df6c1 /drivers/watchdog/octeon-wdt-nmi.S
parentdb470ce8c6ee0efdc4fe699a3293ac2c0a5646f6 (diff)
watchdog: dw_wdt: add stop watchdog operation
[ Upstream commit 1bfe8889380890efe4943d125124f5a7b48571b0 ] The only way of stopping the watchdog is by resetting it. Add the watchdog op for stopping the device and reset if a reset line is provided. At same time WDOG_HW_RUNNING should be remove from dw_wdt_start. As commented by Guenter Roeck: dw_wdt sets WDOG_HW_RUNNING in its open function. Result is that the kref_get() in watchdog_open() won't be executed. But then kref_put() in close will be called since the watchdog now does stop. This causes the imbalance. Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de> Cc: Wim Van Sebroeck <wim@iguana.be> Cc: Guenter Roeck <linux@roeck-us.net> Cc: linux-watchdog@vger.kernel.org Reviewed-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Wim Van Sebroeck <wim@iguana.be> Signed-off-by: Sasha Levin <alexander.levin@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/watchdog/octeon-wdt-nmi.S')
0 files changed, 0 insertions, 0 deletions