Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Kartik Rajput <kkartik@nvidia.com>
Cc: tglx@linutronix.de, thierry.reding@gmail.com,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2] clocksource: timer-tegra186: Enable WDT at probe
Date: Mon, 7 Jul 2025 22:19:06 +0100	[thread overview]
Message-ID: <58d948d3-bbc9-4fca-9393-ce995a4e2567@nvidia.com> (raw)
In-Reply-To: <aGuYuHx5qlKCur8P@mai.linaro.org>


On 07/07/2025 10:51, Daniel Lezcano wrote:
> On Thu, Jul 03, 2025 at 04:34:15PM +0530, 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.
> 
> Please resend with proper recipients (linux-watchdog@, Wim Van
> Sebroeck, Guenter Roeck) and the changelog.

ACK.

> Can someone take the opportunity to split this watchdog code and move
> it in the proper watchdog drivers directory ?

I understand that this was mentioned before, but Thierry previously 
objected to this for this particular driver [0].

Cheers,
Jon

[0] 
https://lore.kernel.org/linux-tegra/4ks74upuufmt2ibh5ur5zpazvfj66ak4gyq7v4rtz2zi2u5wsi@rls64ws3rukp/

-- 
nvpublic


  reply	other threads:[~2025-07-07 21:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 11:04 [PATCH v2] clocksource: timer-tegra186: Enable WDT at probe Kartik Rajput
2025-07-07  9:51 ` Daniel Lezcano
2025-07-07 21:19   ` Jon Hunter [this message]
2025-07-07 22:03     ` Daniel Lezcano
2025-07-08 11:22       ` Thierry Reding
2025-07-08 11:42         ` Jon Hunter
2025-07-08 14:10           ` Daniel Lezcano

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=58d948d3-bbc9-4fca-9393-ce995a4e2567@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