All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: "Tom Rini" <trini@konsulko.com>,
	"Francesco Dolcini" <francesco.dolcini@toradex.com>,
	"Łukasz Majewski" <lukma@nabladev.com>,
	"Thierry Reding" <treding@nvidia.com>,
	u-boot@lists.denx.de, "Stephen Warren" <swarren@nvidia.com>
Subject: Re: [PATCH 1/2] timer: tegra: Bind watchdog driver when timer node is processed
Date: Wed, 10 Sep 2025 10:51:48 +0200	[thread overview]
Message-ID: <20250910085148.GA9815@francesco-nb> (raw)
In-Reply-To: <CAPVz0n0Yk8GzX7Y3qUET2EK=UWyGwn7FLn5HGfLP7i9ms9ht2w@mail.gmail.com>

Hello,

On Tue, Sep 09, 2025 at 07:08:34PM +0300, Svyatoslav Ryhel wrote:
> вт, 9 вер. 2025 р. о 18:47 Tom Rini <trini@konsulko.com> пише:
> >
> ...
> > It's a devkit where I'm pretty sure the watchdog exists, so we can
> > enable it there and be done. Just because it doesn't use it today
> > doesn't mean it can't use it in the future if we enable it, the "use
> > watchdog to make sure A/B system configures are stable" is a common use
> > case.
...
> Not sure if changes into colibri_t30_defconfig are needed, but if
> Francesco would like them, then ok.

I would prefer the defconfig not to be touched.

Francesco


  reply	other threads:[~2025-09-10  8:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26  9:39 [PATCH 1/2] timer: tegra: Bind watchdog driver when timer node is processed Lukasz Majewski
2025-08-26  9:39 ` [PATCH 2/2] watchdog: Add implementation of NVIDIA's Tegra 30 watchdog driver Lukasz Majewski
2025-09-17 14:01   ` Svyatoslav Ryhel
2025-08-26 10:10 ` [PATCH 1/2] timer: tegra: Bind watchdog driver when timer node is processed Svyatoslav Ryhel
2025-09-08 12:41   ` Łukasz Majewski
2025-09-08 13:55     ` Svyatoslav Ryhel
2025-09-09 10:15       ` Łukasz Majewski
2025-09-09 11:26         ` Svyatoslav Ryhel
2025-09-09 15:39           ` Tom Rini
2025-09-09 15:44             ` Svyatoslav Ryhel
2025-09-09 15:47               ` Tom Rini
2025-09-09 16:08                 ` Svyatoslav Ryhel
2025-09-10  8:51                   ` Francesco Dolcini [this message]
2025-09-10 12:28                     ` Łukasz Majewski
2025-09-10 14:07                       ` Francesco Dolcini
2025-09-11  6:46                         ` Łukasz Majewski
2025-09-10  6:52                 ` Łukasz Majewski
2025-09-17 12:46 ` Łukasz Majewski
2025-09-17 13:40   ` Svyatoslav Ryhel

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=20250910085148.GA9815@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=clamor95@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=lukma@nabladev.com \
    --cc=swarren@nvidia.com \
    --cc=treding@nvidia.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.