From: sashiko-bot@kernel.org
To: "Stefano Radaelli" <stefano.radaelli21@gmail.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev
Cc: robh@kernel.org, conor+dt@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v1 2/2] arm64: dts: imx93-var-som-symphony: enable UART wakeup
Date: Mon, 02 Nov 2026 19:04:55 +0000 [thread overview]
Message-ID: <sashiko-outbox-193979@kernel.org> (raw)
In-Reply-To: <5e9ae0cbf0b98898a8020bf3d8889fe87405a3d3.1793645417.git.stefano.r@variscite.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] arm64: dts: imx93: invalid and unused wakeup-source property on lpuart1
--
commit 54c0e2db8b2c42ca5d07339b64a64c48881a16ab
Author: Stefano Radaelli <stefano.r@variscite.com>
arm64: dts: imx93-var-som-symphony: enable UART wakeup
This commit adds the wakeup-source property to the lpuart1 node in
imx93-var-som-symphony.dts to enable UART wakeup from system suspend.
> diff --git a/arch/arm64/boot/dts/freescale/imx93-var-som-symphony.dts b/arch/arm64/boot/dts/freescale/imx93-var-som-symphony.dts
> index 1f0954620195a..47203811abe99 100644
> --- a/arch/arm64/boot/dts/freescale/imx93-var-som-symphony.dts
> +++ b/arch/arm64/boot/dts/freescale/imx93-var-som-symphony.dts
> @@ -302,6 +302,7 @@ typec1_dr_sw: endpoint {
> &lpuart1 {
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_uart1>;
> + wakeup-source;
[Severity: Medium]
Is wakeup-source supported by the fsl-lpuart binding and driver here?
In arch/arm64/boot/dts/freescale/imx91_93_common.dtsi, lpuart1 uses the
compatible strings fsl,imx93-lpuart, fsl,imx8ulp-lpuart, and
fsl,imx7ulp-lpuart, which bind against
Documentation/devicetree/bindings/serial/fsl-lpuart.yaml. That schema
only references serial.yaml and rs485.yaml and specifies:
unevaluatedProperties: false
Neither fsl-lpuart.yaml, serial.yaml, nor rs485.yaml defines
wakeup-source, so adding it to &lpuart1 causes a dtbs_check validation
failure.
In addition, neither lpuart_probe() in drivers/tty/serial/fsl_lpuart.c
nor serial_core_add_one_port() in drivers/tty/serial/serial_core.c parses
wakeup-source from the UART DT node. Instead, serial_core_add_one_port()
unconditionally marks the tty device wakeup-capable (leaving wakeup
disabled until enabled via sysfs), and lpuart_uport_is_active() checks
that tty device:
drivers/tty/serial/serial_core.c:serial_core_add_one_port() {
...
if (!IS_ERR(tty_dev)) {
device_set_wakeup_capable(tty_dev, 1);
}
...
}
drivers/tty/serial/fsl_lpuart.c:lpuart_uport_is_active() {
...
may_wake = tty_dev && device_may_wakeup(tty_dev);
...
}
Does this property actually have any effect without corresponding binding
and driver support?
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1793645417.git.stefano.r@variscite.com?part=2
prev parent reply other threads:[~2026-11-02 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 18:55 [PATCH v1 0/2] arm64: dts: imx93: enable UART wakeup on Variscite boards Stefano Radaelli
2026-11-02 18:55 ` [PATCH v1 1/2] arm64: dts: imx93-var-dart-sonata: enable UART wakeup Stefano Radaelli
2026-11-02 19:03 ` sashiko-bot
2026-11-02 18:55 ` [PATCH v1 2/2] arm64: dts: imx93-var-som-symphony: " Stefano Radaelli
2026-11-02 19: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=sashiko-outbox-193979@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=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=stefano.radaelli21@gmail.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