public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Kartik Rajput <kkartik@nvidia.com>,
	daniel.lezcano@linaro.org, tglx@linutronix.de,
	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 15:11:57 +0100	[thread overview]
Message-ID: <2b6f9898-9c46-4397-a440-102e21309488@nvidia.com> (raw)
In-Reply-To: <q7fi2hpswm2tsowrtbanlnidxnyq3fyb2xxr6gcowxv6sglhop@nsvwlol4dac3>


On 03/07/2025 14:36, Thierry Reding wrote:

...

> I clearly can't read code today. Seems generally fine, then, but I'm
> actually really enthused now about using a second watchdog for kernel
> petting. Since we don't use any of the other two watchdogs, is there
> any reason why we can't cleanly separate both use-cases? It would let
> us avoid some of these special cases that are not intuitive to
> understand.

The only reason would be if for some reason the other are all allocated 
for other uses outside of the kernel. We are currently only using the 
one for the kernel so that it would mean updating all the device trees 
for all platforms to support this too.

I was also thinking about how do we identify/select if a watchdog is pet 
by the kernel or userspace? I was thinking that the presence of the 
'interrupt' property in device-tree could be used; if present the kernel 
pets and if not assume userspace pets. However, the 'interrupt' property 
is currently marked as required and not optional.

-- 
nvpublic


  reply	other threads:[~2025-07-03 14:12 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 [this message]
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
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=2b6f9898-9c46-4397-a440-102e21309488@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