summaryrefslogtreecommitdiffstats
path: root/drivers/watchdog
diff options
context:
space:
mode:
authorLouis Morhet <lmorhet@kalray.eu>2022-01-17 23:19:13 +0100
committerSascha Hauer <s.hauer@pengutronix.de>2022-01-18 09:07:27 +0100
commit492a9b0f135fb3b0412b8bb63ce535d64fe9ccf9 (patch)
treeaa2f29a0fbb29229809606c8915bb834e41fc710 /drivers/watchdog
parentda51e98d83d66d9b24cfda8b4de13ec0da951ec2 (diff)
downloadbarebox-492a9b0f135fb3b0412b8bb63ce535d64fe9ccf9.tar.gz
barebox-492a9b0f135fb3b0412b8bb63ce535d64fe9ccf9.tar.xz
watchdog: kvx: do not disable watchdog on probe
As the watchdog may be set by a lower stage in the boot chain, and for a good reason (precisely to ensure reliable update when something unexpected happens during the boot chain), it is a bad idea to always disable it during probe. We should either have a mechanism to refresh it on a regular basis in barebox itself and set it to something bigger for Linux, or handle it transparently and let the previous stage set the global watchdog up to Linux. This patch assumes for now the latter. Signed-off-by: Louis Morhet <lmorhet@kalray.eu> Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu> Link: https://lore.barebox.org/20220117221917.26970-8-jmaselbas@kalray.eu Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'drivers/watchdog')
-rw-r--r--drivers/watchdog/kvx_wdt.c4
1 files changed, 1 insertions, 3 deletions
diff --git a/drivers/watchdog/kvx_wdt.c b/drivers/watchdog/kvx_wdt.c
index da19136fda..df9430769b 100644
--- a/drivers/watchdog/kvx_wdt.c
+++ b/drivers/watchdog/kvx_wdt.c
@@ -73,11 +73,9 @@ static int kvx_wdt_drv_probe(struct device_d *dev)
wdd->hwdev = dev;
wdd->set_timeout = kvx_wdt_set_timeout;
- /* Be sure that interrupt are disable */
+ /* Be sure that interrupt are disabled */
kvx_sfr_set_field(TCR, WIE, 0);
- kvx_watchdog_disable();
-
return watchdog_register(wdd);
}