From: Jon Hunter <jonathanh@nvidia.com>
To: Kartik Rajput <kkartik@nvidia.com>,
daniel.lezcano@kernel.org, tglx@kernel.org,
wim@linux-watchdog.org, linux@roeck-us.net,
thierry.reding@kernel.org, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 0/4] Add support for Kernel WDT
Date: Thu, 4 Jun 2026 09:49:37 +0100 [thread overview]
Message-ID: <b286735a-10e1-4446-8df3-9071e6e73de7@nvidia.com> (raw)
In-Reply-To: <a53437c2-1f39-43e8-9d94-3f0867a557a9@nvidia.com>
Hi Daniel,
On 12/05/2026 14:56, Jon Hunter wrote:
>
> On 07/05/2026 16:45, Kartik Rajput wrote:
>> Tegra186 and later SoCs support multiple watchdog timers in the TKE
>> block, the driver so far only uses WDT0. This series extends it to
>> make use of the additional instances and reserve the first available WDT
>> for Kernel.
>>
>> Patch 1 fixes a read-modify-write bug in tegra186_wdt_enable()
>> that would otherwise make registering more than one watchdog unsafe.
>>
>> Patch 2 corrects num_wdts for Tegra186 and Tegra234. WDT2 is connected
>> to the Audio Processing Engine (APE) and cannot be accessed from Linux,
>> so only WDT0 and WDT1 are available.
>>
>> Patch 3 iterates over all WDTs and registers the ones whose TKE SCR
>> firewall grants OS access.
>>
>> Patch 4 reserves the first accessible watchdog as a kernel-only
>> watchdog, arms it at probe with a 120 s timeout, and pets it from
>> the driver's IRQ handler, it is not exposed to userspace, so the
>> system can still reset if the kernel hangs before userspace opens a
>> watchdog.
>>
>> Kartik Rajput (4):
>> clocksource/drivers/timer-tegra186: Fix support for multiple watchdog
>> instances
>> clocksource/drivers/timer-tegra186: Correct num_wdts for Tegra186 and
>> Tegra234
>> clocksource/drivers/timer-tegra186: Register all accessible watchdog
>> timers
>> clocksource/drivers/timer-tegra186: Reserve and service a kernel
>> watchdog
>>
>> drivers/clocksource/timer-tegra186.c | 122 +++++++++++++++++++++++----
>> 1 file changed, 104 insertions(+), 18 deletions(-)
>>
>
> For the series ...
>
> Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Are you OK to pick this up? We would like to get this into -next if
there are no objections.
Thanks
Jon
--
nvpublic
prev parent reply other threads:[~2026-06-04 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 15:45 Kartik Rajput
2026-05-07 15:45 ` [PATCH 1/4] clocksource/drivers/timer-tegra186: Fix support for multiple watchdog instances Kartik Rajput
2026-06-13 14:33 ` [tip: timers/clocksource] " tip-bot2 for Kartik Rajput
2026-05-07 15:45 ` [PATCH 2/4] clocksource/drivers/timer-tegra186: Correct num_wdts for Tegra186 and Tegra234 Kartik Rajput
2026-06-13 14:33 ` [tip: timers/clocksource] " tip-bot2 for Kartik Rajput
2026-05-07 15:45 ` [PATCH 3/4] clocksource/drivers/timer-tegra186: Register all accessible watchdog timers Kartik Rajput
2026-06-13 14:33 ` [tip: timers/clocksource] " tip-bot2 for Kartik Rajput
2026-05-07 15:45 ` [PATCH 4/4] clocksource/drivers/timer-tegra186: Reserve and service a kernel watchdog Kartik Rajput
2026-06-13 14:32 ` [tip: timers/clocksource] " tip-bot2 for Kartik Rajput
2026-05-12 13:56 ` [PATCH 0/4] Add support for Kernel WDT Jon Hunter
2026-06-04 8:49 ` Jon Hunter [this message]
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=b286735a-10e1-4446-8df3-9071e6e73de7@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=daniel.lezcano@kernel.org \
--cc=kkartik@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=tglx@kernel.org \
--cc=thierry.reding@kernel.org \
--cc=wim@linux-watchdog.org \
/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