From: Julian Vetter <jvetter@kalrayinc.com>
To: barebox@lists.infradead.org
Cc: Yann Sionneau <ysionneau@kalrayinc.com>,
Jules Maselbas <jmaselbas@kalray.eu>,
Julian Vetter <jvetter@kalrayinc.com>
Subject: [PATCH v2] kvx: watchdog: Add early watchdog init
Date: Thu, 24 Oct 2024 15:08:03 +0200 [thread overview]
Message-ID: <20241024130803.2208041-1-jvetter@kalrayinc.com> (raw)
From: Jules Maselbas <jmaselbas@kalray.eu>
Add support for a watchdog that starts as early as possible in barebox.
So, if there is an issue the board is reset properly.
Signed-off-by: Julian Vetter <jvetter@kalrayinc.com>
---
drivers/watchdog/Kconfig | 11 +++++++++++
drivers/watchdog/kvx_wdt.c | 16 ++++++++++++++++
2 files changed, 27 insertions(+)
diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
index 762e37c9c2..71bc7bf0ac 100644
--- a/drivers/watchdog/Kconfig
+++ b/drivers/watchdog/Kconfig
@@ -89,6 +89,17 @@ config WATCHDOG_KVX
help
Add support for the KVX core watchdog.
+config WATCHDOG_KVX_EARLY_INIT
+ bool "KVX Core watchdog early init"
+ depends on WATCHDOG_KVX
+ help
+ Activate the watchdog with early initcall
+
+config WATCHDOG_KVX_EARLY_TIMEOUT
+ int "KVX Core watchdog early timeout in cycles"
+ depends on WATCHDOG_KVX_EARLY_INIT
+ default 100000000
+
config WATCHDOG_BCM2835
bool "Watchdog for BCM283x SoCs"
depends on ARCH_BCM283X || COMPILE_TEST
diff --git a/drivers/watchdog/kvx_wdt.c b/drivers/watchdog/kvx_wdt.c
index be6b08b71c..3e66aa38ba 100644
--- a/drivers/watchdog/kvx_wdt.c
+++ b/drivers/watchdog/kvx_wdt.c
@@ -91,3 +91,19 @@ static struct driver kvx_wdt_driver = {
.of_compatible = DRV_OF_COMPAT(kvx_wdt_of_match),
};
device_platform_driver(kvx_wdt_driver);
+
+#ifdef CONFIG_WATCHDOG_KVX_EARLY_INIT
+static int kvx_wdt_early_init(void)
+{
+ /* Set Start watchdog counting */
+ kvx_sfr_set(WDV, CONFIG_WATCHDOG_KVX_EARLY_TIMEOUT);
+ kvx_sfr_set(WDR, 0);
+
+ /* Start watchdog counting */
+ kvx_sfr_set_field(TCR, WUI, 1);
+ kvx_sfr_set_field(TCR, WCE, 1);
+
+ return 0;
+}
+core_initcall(kvx_wdt_early_init);
+#endif
--
2.34.1
next reply other threads:[~2024-10-24 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 13:08 Julian Vetter [this message]
2024-10-24 13:23 ` Ahmad Fatoum
2024-10-25 6:32 ` Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241024130803.2208041-1-jvetter@kalrayinc.com \
--to=jvetter@kalrayinc.com \
--cc=barebox@lists.infradead.org \
--cc=jmaselbas@kalray.eu \
--cc=ysionneau@kalrayinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox