From: sashiko-bot@kernel.org
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: conor+dt@kernel.org, linux-watchdog@vger.kernel.org,
wsa+renesas@sang-engineering.com, devicetree@vger.kernel.org,
robh@kernel.org
Subject: Re: [PATCH RFC v2 8/9] arm64: dts: renesas: r9a09g077: Use SYS syscon for WDTDCR access
Date: Thu, 02 Jul 2026 12:44:54 +0000 [thread overview]
Message-ID: <20260702124455.74FD01F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260702123112.161160-9-prabhakar.mahadev-lad.rj@bp.renesas.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Transitioning to a syscon regmap introduces a spinlock into the watchdog restart path, creating a severe deadlock risk during kernel panics or reboots.
--
commit f54f749e298c48411aae186783c11b3cc40d3738
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
arm64: dts: renesas: r9a09g077: Use SYS syscon for WDTDCR access
This commit updates the device tree for the r9a09g077 watchdog nodes
to use the new System Controller (SYS) syscon interface. It replaces
the direct MMIO region mapping with a "renesas,sys" phandle.
> diff --git a/arch/arm64/boot/dts/renesas/r9a09g077.dtsi b/arch/arm64/boot/dts/renesas/r9a09g077.dtsi
> index 208287f7b7442..ae69a01d60427 100644
> --- a/arch/arm64/boot/dts/renesas/r9a09g077.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r9a09g077.dtsi
> @@ -327,61 +327,61 @@ channel1 {
>
> wdt0: watchdog@80082000 {
> compatible = "renesas,r9a09g077-wdt";
> - reg = <0 0x80082000 0 0x400>,
> - <0 0x81295100 0 0x04>;
> + reg = <0 0x80082000 0 0x400>;
> clocks = <&cpg CPG_CORE R9A09G077_CLK_PCLKL>;
> clock-names = "pclk";
> power-domains = <&cpg>;
> + renesas,sys = <&sys1 0>;
[Severity: High]
Does adding this property introduce a deadlock during system panic or reboot?
By pointing the watchdog at the syscon regmap, the driver transitions
from lockless MMIO to a spinlocked regmap access path. If the system panics
and smp_send_stop() stops a CPU while it is holding the syscon regmap lock,
the watchdog restart handler could hang indefinitely.
The triggering sequence looks like this:
machine_restart()
smp_send_stop()
do_kernel_restart()
watchdog_restart_notifier()
rzv2h_wdt_restart()
rzt2h_wdt_wdtdcr_count_start()
regmap_update_bits()
Since regmap_update_bits() uses a standard spinlock, the restart path will
spin forever waiting for the locked CPU. Is there a way to bypass the lock
during the restart sequence?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260702123112.161160-1-prabhakar.mahadev-lad.rj@bp.renesas.com?part=8
next prev parent reply other threads:[~2026-07-02 12:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 12:31 [PATCH RFC v2 0/9] Add System Controller support for RZ/T2H and RZ/N2H SoCs Prabhakar
2026-07-02 12:31 ` [PATCH RFC v2 1/9] dt-bindings: clock: renesas,cpg-mssr: Support RZ/T2H system controllers Prabhakar
2026-07-02 12:38 ` sashiko-bot
2026-07-02 12:31 ` [PATCH RFC v2 2/9] clk: renesas: r9a09g077: Add SYSC regmap support Prabhakar
2026-07-02 12:48 ` sashiko-bot
2026-07-02 12:31 ` [PATCH RFC v2 3/9] arm64: dts: renesas: r9a09g077: Add system controller child nodes Prabhakar
2026-07-02 12:31 ` [PATCH RFC v2 4/9] arm64: dts: renesas: r9a09g087: " Prabhakar
2026-07-02 12:31 ` [PATCH RFC v2 5/9] dt-bindings: watchdog: renesas,r9a09g057-wdt: Add SYS syscon support Prabhakar
2026-07-02 12:38 ` sashiko-bot
2026-07-02 12:31 ` [PATCH RFC v2 6/9] watchdog: rzv2h: Refactor WDTDCR start/stop handling Prabhakar
2026-07-02 12:31 ` [PATCH RFC v2 7/9] watchdog: rzv2h: Add syscon support for RZ/T2H and RZ/N2H WDT control register Prabhakar
2026-07-02 12:42 ` sashiko-bot
2026-07-02 13:27 ` Guenter Roeck
2026-07-02 15:12 ` Lad, Prabhakar
2026-07-02 12:31 ` [PATCH RFC v2 8/9] arm64: dts: renesas: r9a09g077: Use SYS syscon for WDTDCR access Prabhakar
2026-07-02 12:44 ` sashiko-bot [this message]
2026-07-02 12:31 ` [PATCH RFC v2 9/9] arm64: dts: renesas: r9a09g087: " Prabhakar
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=20260702124455.74FD01F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.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