From: sashiko-bot@kernel.org
To: "Artur Kowalski" <arturkow2000@gmail.com>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 1/6] clocksource/drivers/timer-tegra: Keep Tegra20's watchdog timers free
Date: Tue, 10 Nov 2026 12:48:42 +0000 [thread overview]
Message-ID: <sashiko-outbox-207046@kernel.org> (raw)
In-Reply-To: <20261110-t20-for-upstream-v1-1-5923449951fe@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] clocksource/drivers/timer-tegra: missing Fixes trailer for
f6d50ec5f85c
--
commit 65df25a211b643454125037a766cc25969d41802
Author: Artur Kowalski <arturkow2000@gmail.com>
> clocksource/drivers/timer-tegra: Keep Tegra20's watchdog timers free
>
> Tegra20 has no watchdog block. Instead, the clock and reset controller
> resets the system when the interrupt of TIMER1 or TIMER2 fires while
> the previous one is still pending. A bootloader can start this watchdog
> and leave it running for the kernel.
>
> Since commit f6d50ec5f85c ("clocksource/drivers/tegra: Support per-CPU
> timers on all Tegra's"), the driver uses TIMER1-2 as the per-CPU clock
> event devices on Tegra20, where it used TIMER3 before. When CPU0's
> clock event device takes over TIMER1, the clock and reset controller
> still resets the system if a timer interrupt fires while the previous
> one hasn't been handled yet, which resets about half of the boots
> early. If the system survives that, the watchdog stays enabled but
> never fires, as CPU0 keeps clearing the timer's interrupts.
>
> Use TIMER3-4 for the per-CPU clock event devices on Tegra20, leaving
> TIMER1-2 to the watchdog. Tegra30 needs TIMER1-4 for its four CPUs and
> its watchdog uses TIMER5, so keep its mapping.
>
> A watchdog left running by the bootloader is then no longer disarmed,
> so it resets the system unless it is pinged. That needs the tegra_wdt
> driver, which gains Tegra20 support in the following patches, built in
> or loaded before the watchdog's timeout expires.
>
> Assisted-by: Claude:claude-opus-5-5
> Signed-off-by: Artur Kowalski <arturkow2000@gmail.com>
[Severity: Low]
This fixes a boot regression introduced by the commit cited in the
changelog. Should this include:
Fixes: f6d50ec5f85c ("clocksource/drivers/tegra: Support per-CPU timers on all Tegra's")
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110-t20-for-upstream-v1-0-5923449951fe@gmail.com?part=1
next prev parent reply other threads:[~2026-11-10 12:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 12:39 [PATCH 0/6] watchdog: tegra_wdt: Add Tegra20 support Artur Kowalski
2026-11-10 12:39 ` [PATCH 1/6] clocksource/drivers/timer-tegra: Keep Tegra20's watchdog timers free Artur Kowalski
2026-11-10 12:48 ` sashiko-bot [this message]
2026-11-10 12:39 ` [PATCH 2/6] watchdog: tegra_wdt: Move SoC specific parts into match data Artur Kowalski
2026-11-10 12:39 ` [PATCH 3/6] watchdog: tegra_wdt: Support Tegra20 Artur Kowalski
2026-11-10 16:21 ` Krzysztof Kozlowski
2026-11-10 12:39 ` [PATCH 4/6] soc/tegra: pmc: Add an option to keep the VDE partition on Artur Kowalski
2026-11-10 12:39 ` [PATCH 5/6] soc/tegra: pmc: Add a partition power off notifier Artur Kowalski
2026-11-10 12:39 ` [PATCH 6/6] watchdog: tegra_wdt: Stop on Tegra20 VDE power off Artur Kowalski
2026-11-10 12:56 ` sashiko-bot
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=sashiko-outbox-207046@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=arturkow2000@gmail.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.