From: sashiko-bot@kernel.org
To: "Diogo Ivo" <diogo.ivo@bootlin.com>
Cc: devicetree@vger.kernel.org, linux-watchdog@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 3/3] arm: dts: ti: omap: Prevent watchdog from being reset on kernel boot
Date: Fri, 11 Sep 2026 09:30:25 +0000 [thread overview]
Message-ID: <20260911093025.DBDD01F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260911-omap4-wdt_boot-v1-3-637d778a4a1e@bootlin.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The patch exposes the system to unexpected reboots due to a 30-second window before the watchdog is idled, contrary to the '3 second window' claimed in the commit message.
--
commit 1abe23cd5472149baeeab9af481deaf65caccd1f
Author: Diogo Ivo <diogo.ivo@bootlin.com>
Subject: arm: dts: ti: omap: Prevent watchdog from being reset on kernel boot
This commit prevents the watchdog from being reset and idled during kernel
boot by adding the ti,no-reset-on-init property to the target-module node.
This is intended to provide a 3-second window for the watchdog driver to
probe without resetting the watchdog.
> diff --git a/arch/arm/boot/dts/ti/omap/omap4-l4.dtsi b/arch/arm/boot/dts/ti/omap/omap4-l4.dtsi
> index 4c78a0b28fab3..e061ea3fc8e70 100644
> --- a/arch/arm/boot/dts/ti/omap/omap4-l4.dtsi
> +++ b/arch/arm/boot/dts/ti/omap/omap4-l4.dtsi
> @@ -1126,6 +1126,7 @@ target-module@4000 { /* 0x4a314000, ap 7 18.0 */
> <SYSC_IDLE_SMART>,
> <SYSC_IDLE_SMART_WKUP>;
> ti,syss-mask = <1>;
> + ti,no-reset-on-init;
[Severity: High]
Does adding this property unintentionally cause a regression where the system
experiences unexpected reboots due to a 30-second delay instead of the
intended 3-second window?
Adding ti,no-reset-on-init skips the immediate hardware reset and triggers the
delayed work fallback in sysc_probe():
drivers/bus/ti-sysc.c:sysc_probe() {
...
schedule_delayed_work(&ddata->idle_work, 3000);
...
}
Because schedule_delayed_work() takes its delay in jiffies rather than
milliseconds, passing 3000 evaluates to 3000 jiffies. On typical ARM
configurations where HZ=100 (the default), this results in a 30-second delay
instead of the expected 3 seconds.
This could lead to a boot loop if the bootloader configures a watchdog timeout
of less than 30 seconds and the system relies on the driver to stop it.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260911-omap4-wdt_boot-v1-0-637d778a4a1e@bootlin.com?part=3
next prev parent reply other threads:[~2026-09-11 9:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 9:17 [PATCH 0/3] watchdog: omap: Preserve OMAP watchdog across boot to detect faulty boots Diogo Ivo
2026-09-11 9:17 ` [PATCH 1/3] watchdog: omap: Remove duplicate start() with early_init Diogo Ivo
2026-09-11 9:29 ` sashiko-bot
2026-09-11 15:09 ` Diogo Ivo
2026-09-11 9:17 ` [PATCH 2/3] watchdog: omap: Add support for reading boot status Diogo Ivo
2026-09-11 9:30 ` sashiko-bot
2026-09-11 15:11 ` Diogo Ivo
2026-09-11 9:17 ` [PATCH 3/3] arm: dts: ti: omap: Prevent watchdog from being reset on kernel boot Diogo Ivo
2026-09-11 9:30 ` sashiko-bot [this message]
2026-09-11 15:13 ` Diogo Ivo
2026-09-11 14:29 ` [PATCH 0/3] watchdog: omap: Preserve OMAP watchdog across boot to detect faulty boots Guenter Roeck
2026-09-11 15:17 ` Diogo Ivo
2026-09-11 17:25 ` Guenter Roeck
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=20260911093025.DBDD01F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=diogo.ivo@bootlin.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox