From: sashiko-bot@kernel.org
To: "Thomas Perrot (Schneider Electric)" <thomas.perrot@bootlin.com>
Cc: conor+dt@kernel.org, linux-watchdog@vger.kernel.org,
imx@lists.linux.dev, robh@kernel.org, devicetree@vger.kernel.org,
Frank.Li@kernel.org
Subject: Re: [PATCH v8 5/5] watchdog: aaeon: Add watchdog driver for SRG-IMX8P MCU
Date: Fri, 31 Jul 2026 10:04:33 +0000 [thread overview]
Message-ID: <20260731100434.195B51F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260731-dev-b4-aaeon-mcu-driver-v8-5-9ab00e80df2a@bootlin.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Contradiction between driver code and DT binding regarding timeout-sec property
--
--- Patch [5]: [PATCH v8 5/5] watchdog: aaeon: Add watchdog driver for SRG-IMX8P MCU ---
commit fca789df9bd6f6279b387ae274aa7dc26fa4cecd
Author: Thomas Perrot (Schneider Electric) <thomas.perrot@bootlin.com>
watchdog: aaeon: Add watchdog driver for SRG-IMX8P MCU
Add watchdog driver for the Aaeon SRG-IMX8P embedded controller.
This driver provides system monitoring and recovery capabilities
through the MCU's watchdog timer.
> diff --git a/drivers/watchdog/aaeon_mcu_wdt.c b/drivers/watchdog/aaeon_mcu_wdt.c
> new file mode 100644
> index 0000000000000..661d14393c6ec
> --- /dev/null
> +++ b/drivers/watchdog/aaeon_mcu_wdt.c
[ ... ]
> +static int aaeon_mcu_wdt_probe(struct platform_device *pdev)
> +{
[ ... ]
> + /*
> + * The MCU firmware has a fixed hardware timeout of 25 seconds that
> + * cannot be changed. The watchdog core handles automatic pinging to
> + * support software timeouts longer than the hardware limit. The default
> + * software timeout of 240 seconds can be overridden via the DT
> + * timeout-sec property or the watchdog_timeout kernel boot parameter.
> + */
> + wdt->timeout = AAEON_MCU_WDT_TIMEOUT;
> + wdt->min_timeout = AAEON_MCU_WDT_MIN_TIMEOUT;
> + wdt->max_hw_heartbeat_ms = AAEON_MCU_WDT_HEARTBEAT_MS;
> + watchdog_init_timeout(wdt, timeout, dev->parent);
[Severity: Medium]
Will this cause device tree validation failures when users specify the
timeout-sec property?
The driver code and comment indicate that the timeout can be overridden via
the DT timeout-sec property on the parent node. However, the DT schema for
the parent MFD (Documentation/devicetree/bindings/mfd/aaeon,srg-imx8p-mcu.yaml)
enforces additionalProperties: false and does not define the timeout-sec
property.
If a user follows the driver's instructions and adds the timeout-sec property
to the MFD parent node, dtbs_check will fail. Should the timeout-sec property
be added to the DT binding?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260731-dev-b4-aaeon-mcu-driver-v8-0-9ab00e80df2a@bootlin.com?part=5
prev parent reply other threads:[~2026-07-31 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 9:51 [PATCH v8 0/5] Add support for AAEON SRG-IMX8P MCU Thomas Perrot (Schneider Electric)
2026-07-31 9:51 ` [PATCH v8 1/5] dt-bindings: vendor-prefixes: Add AAEON vendor prefix Thomas Perrot (Schneider Electric)
2026-07-31 9:51 ` [PATCH v8 2/5] dt-bindings: mfd: Add AAEON embedded controller Thomas Perrot (Schneider Electric)
2026-07-31 9:51 ` [PATCH v8 3/5] mfd: aaeon: Add SRG-IMX8P MCU driver Thomas Perrot (Schneider Electric)
2026-07-31 10:07 ` sashiko-bot
2026-07-31 9:51 ` [PATCH v8 4/5] gpio: aaeon: Add GPIO driver for SRG-IMX8P MCU Thomas Perrot (Schneider Electric)
2026-07-31 10:01 ` sashiko-bot
2026-07-31 9:51 ` [PATCH v8 5/5] watchdog: aaeon: Add watchdog " Thomas Perrot (Schneider Electric)
2026-07-31 10:04 ` sashiko-bot [this message]
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=20260731100434.195B51F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=linux-watchdog@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=thomas.perrot@bootlin.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