From: sashiko-bot@kernel.org
To: "Wolfram Sang" <wsa+renesas@sang-engineering.com>
Cc: linux-watchdog@vger.kernel.org, wsa+renesas@sang-engineering.com
Subject: Re: [PATCH v4 3/4] watchdog: rzn1: remove now obsolete interrupt support
Date: Thu, 07 May 2026 21:05:40 +0000 [thread overview]
Message-ID: <20260507210540.EB205C2BCB2@smtp.kernel.org> (raw)
In-Reply-To: <20260507102410.43384-4-wsa+renesas@sang-engineering.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Unconditionally removing the interrupt workaround breaks watchdog reboot functionality on existing systems running older bootloaders.
--
commit cc090392d96a1601fdb1492a2e01bab3e4a23303
Author: Wolfram Sang <wsa+renesas@sang-engineering.com>
watchdog: rzn1: remove now obsolete interrupt support
This commit removes the interrupt-based workaround that used
emergency_restart() on watchdog timeout. It assumes the controller is now
configured by the bootloader to reset the system directly.
> diff --git a/drivers/watchdog/rzn1_wdt.c b/drivers/watchdog/rzn1_wdt.c
> --- a/drivers/watchdog/rzn1_wdt.c
> +++ b/drivers/watchdog/rzn1_wdt.c
[ ... ]
> @@ -116,15 +106,6 @@ static int rzn1_wdt_probe(struct platform_device *pdev)
> if (IS_ERR(wdt->base))
> return PTR_ERR(wdt->base);
>
> - irq = platform_get_irq(pdev, 0);
> - if (irq < 0)
> - return irq;
> -
> - ret = devm_request_irq(dev, irq, rzn1_wdt_irq, 0,
> - np->name, wdt);
> - if (ret)
> - return dev_err_probe(dev, ret, "failed to request irq %d\n", irq);
Will this break existing systems running older bootloaders?
If the bootloader hasn't been updated to configure the hardware for direct
reset, the watchdog timeout will assert the interrupt line. Without this
handler, the unhandled interrupt might cause the system to hang entirely
instead of rebooting.
Could we use platform_get_irq_optional() here instead and retain the
interrupt handler as a fallback for backward compatibility with older
firmware?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260507102410.43384-1-wsa+renesas@sang-engineering.com?part=3
next prev parent reply other threads:[~2026-05-07 21:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 10:24 [PATCH v4 0/4] watchdog: rzn1: clean up and drop irq requirement Wolfram Sang
2026-05-07 10:24 ` [PATCH v4 1/4] watchdog: rzn1: Fix reverse xmas tree declaration Wolfram Sang
2026-05-08 16:29 ` Guenter Roeck
2026-05-07 10:24 ` [PATCH v4 2/4] watchdog: rzn1: Use dev_err_probe() Wolfram Sang
2026-05-08 16:30 ` Guenter Roeck
2026-05-07 10:24 ` [PATCH v4 3/4] watchdog: rzn1: remove now obsolete interrupt support Wolfram Sang
2026-05-07 11:20 ` Herve Codina
2026-05-07 21:05 ` sashiko-bot [this message]
2026-05-08 16:31 ` Guenter Roeck
2026-05-08 20:05 ` Wolfram Sang
2026-05-07 10:24 ` [PATCH v4 4/4] dt-bindings: watchdog: renesas,rzn1-wdt: interrupts are not required Wolfram Sang
2026-05-07 11:22 ` Herve Codina
2026-05-08 16:32 ` Guenter Roeck
2026-05-13 22:28 ` Rob Herring (Arm)
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=20260507210540.EB205C2BCB2@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=sashiko@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