From: Jon Hunter <jonathanh@nvidia.com>
To: Kartik Rajput <kkartik@nvidia.com>,
daniel.lezcano@linaro.org, tglx@linutronix.de,
thierry.reding@gmail.com, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH] clocksource: timer-tegra186: Enable WDT at probe
Date: Thu, 3 Jul 2025 11:36:16 +0100 [thread overview]
Message-ID: <458d9b45-2879-4dd5-b164-82d87fdb5ad8@nvidia.com> (raw)
In-Reply-To: <20250630110135.201930-1-kkartik@nvidia.com>
On 30/06/2025 12:01, Kartik Rajput wrote:
> Currently, if the system crashes or hangs during kernel boot before
> userspace initializes and configures the watchdog timer, then the
> watchdog won’t be able to recover the system as it’s not running. This
> becomes crucial during an over-the-air update, where if the newly
> updated kernel crashes on boot, the watchdog is needed to reset the
> device and boot into an alternative system partition. If the watchdog
> is disabled in such scenarios, it can lead to the system getting
> bricked.
>
> Enable the WDT during driver probe to allow recovery from any crash/hang
> seen during early kernel boot. Also, disable interrupts once userspace
> starts pinging the watchdog.
>
> Signed-off-by: Kartik Rajput <kkartik@nvidia.com>
> ---
> drivers/clocksource/timer-tegra186.c | 42 ++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
>
> diff --git a/drivers/clocksource/timer-tegra186.c b/drivers/clocksource/timer-tegra186.c
> index e5394f98a02e..59abb5dab8f1 100644
> --- a/drivers/clocksource/timer-tegra186.c
> +++ b/drivers/clocksource/timer-tegra186.c
> @@ -57,6 +57,8 @@
> #define WDTUR 0x00c
> #define WDTUR_UNLOCK_PATTERN 0x0000c45a
>
> +#define WDT_DEFAULT_TIMEOUT 120
> +
> struct tegra186_timer_soc {
> unsigned int num_timers;
> unsigned int num_wdts;
> @@ -74,6 +76,7 @@ struct tegra186_wdt {
>
> void __iomem *regs;
> unsigned int index;
> + bool enable_irq;
> bool locked;
>
> struct tegra186_tmr *tmr;
> @@ -174,6 +177,12 @@ static void tegra186_wdt_enable(struct tegra186_wdt *wdt)
> value &= ~WDTCR_PERIOD_MASK;
> value |= WDTCR_PERIOD(1);
>
> + /* configure local interrupt for WDT petting */
It might be a bit clearer if this comment states ...
'If enable_irq is set then enable the watchdog IRQ for kernel petting,
otherwise userspace is responsible for petting the watchdog.'
> + if (wdt->enable_irq)
> + value |= WDTCR_LOCAL_INT_ENABLE;
> + else
> + value &= ~WDTCR_LOCAL_INT_ENABLE;
> +
> /* enable system POR reset */
> value |= WDTCR_SYSTEM_POR_RESET_ENABLE;
>
> @@ -205,6 +214,10 @@ static int tegra186_wdt_ping(struct watchdog_device *wdd)
> {
> struct tegra186_wdt *wdt = to_tegra186_wdt(wdd);
>
> + /* Disable WDT interrupt once userspace takes over. */
Technically userspace is taking over at this point and so we should be
more assertive here ...
'Disable the watchdog IRQ now userspace is taking over'
> + if (wdt->enable_irq)
> + wdt->enable_irq = false;
> +
> tegra186_wdt_disable(wdt);
> tegra186_wdt_enable(wdt);
>
> @@ -315,6 +328,8 @@ static struct tegra186_wdt *tegra186_wdt_create(struct tegra186_timer *tegra,
> if (value & WDTCR_LOCAL_INT_ENABLE)
> wdt->locked = true;
>
> + wdt->enable_irq = true;
> +
> source = value & WDTCR_TIMER_SOURCE_MASK;
>
> wdt->tmr = tegra186_tmr_create(tegra, source);
> @@ -339,6 +354,13 @@ static struct tegra186_wdt *tegra186_wdt_create(struct tegra186_timer *tegra,
> return ERR_PTR(err);
> }
>
> + /*
> + * Start the watchdog to recover the system if it crashes before
> + * userspace initialize the WDT.
> + */
> + tegra186_wdt_set_timeout(&wdt->base, WDT_DEFAULT_TIMEOUT);
> + tegra186_wdt_start(&wdt->base);
> +
> return wdt;
> }
>
> @@ -415,10 +437,21 @@ static int tegra186_timer_usec_init(struct tegra186_timer *tegra)
> return clocksource_register_hz(&tegra->usec, USEC_PER_SEC);
> }
>
> +static irqreturn_t tegra186_timer_irq(int irq, void *data)
> +{
> + struct tegra186_timer *tegra = data;
> +
> + tegra186_wdt_disable(tegra->wdt);
> + tegra186_wdt_enable(tegra->wdt);
> +
> + return IRQ_HANDLED;
> +}
> +
> static int tegra186_timer_probe(struct platform_device *pdev)
> {
> struct device *dev = &pdev->dev;
> struct tegra186_timer *tegra;
> + unsigned int irq;
> int err;
>
> tegra = devm_kzalloc(dev, sizeof(*tegra), GFP_KERNEL);
> @@ -437,6 +470,15 @@ static int tegra186_timer_probe(struct platform_device *pdev)
> if (err < 0)
> return err;
>
> + irq = err;
> +
> + err = devm_request_irq(dev, irq, tegra186_timer_irq, 0,
> + "tegra186-timer", tegra);
> + if (err < 0) {
> + dev_err(dev, "failed to request IRQ#%u: %d\n", irq, err);
> + return err;
> + }
> +
> /* create a watchdog using a preconfigured timer */
> tegra->wdt = tegra186_wdt_create(tegra, 0);
> if (IS_ERR(tegra->wdt)) {
--
nvpublic
next prev parent reply other threads:[~2025-07-03 10:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 11:01 [PATCH] clocksource: timer-tegra186: Enable WDT at probe Kartik Rajput
2025-07-03 6:55 ` Thierry Reding
2025-07-03 7:55 ` Jon Hunter
2025-07-03 10:12 ` Thierry Reding
2025-07-03 10:26 ` Jon Hunter
2025-07-03 13:36 ` Thierry Reding
2025-07-03 14:11 ` Jon Hunter
2025-07-03 14:19 ` Thierry Reding
2025-07-03 14:42 ` Jon Hunter
2025-07-03 8:23 ` Kartik Rajput
2025-07-03 10:36 ` Jon Hunter [this message]
2025-07-03 13:40 ` Thierry Reding
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=458d9b45-2879-4dd5-b164-82d87fdb5ad8@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=daniel.lezcano@linaro.org \
--cc=kkartik@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.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