Devicetree
 help / color / mirror / Atom feed
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 1/2] arm64: dts: imx93-var-dart-sonata: enable UART wakeup
Date: Mon, 02 Nov 2026 19:03:54 +0000	[thread overview]
Message-ID: <sashiko-outbox-193978@kernel.org> (raw)
In-Reply-To: <b51bef917d08b83bd231a4a228fb2d23c19a858b.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-var-dart-sonata: invalid wakeup-source on lpuart1
--

commit 65667fa7cde1bed5fd9129933907d0e5e0428a2f
Author: Stefano Radaelli <stefano.r@variscite.com>

arm64: dts: imx93-var-dart-sonata: enable UART wakeup

This commit adds the wakeup-source property to the lpuart1 node in
imx93-var-dart-sonata.dts to allow the serial console to wake the system from
suspend.

> diff --git a/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata.dts b/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata.dts
> index 1ca3ec8330d07..d368a09dc9167 100644
> --- a/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata.dts
> +++ b/arch/arm64/boot/dts/freescale/imx93-var-dart-sonata.dts
> @@ -385,6 +385,7 @@ can0: can@0 {
>  &lpuart1 {
>  	pinctrl-names = "default";
>  	pinctrl-0 = <&pinctrl_uart1>;
> +	wakeup-source;

[Severity: Medium]
Does adding wakeup-source to &lpuart1 pass dtbs_check or take effect at
runtime?

The lpuart1 node in arch/arm64/boot/dts/freescale/imx91_93_common.dtsi uses
the "fsl,imx93-lpuart", "fsl,imx8ulp-lpuart", "fsl,imx7ulp-lpuart"
compatibles, which are matched by
Documentation/devicetree/bindings/serial/fsl-lpuart.yaml:

  required:
    - compatible
    - reg
    - interrupts
    - clocks
    - clock-names

  unevaluatedProperties: false

Neither fsl-lpuart.yaml nor the schemas it references (serial.yaml and
rs485.yaml) define wakeup-source, so this causes an unevaluated property
validation failure on serial@44380000.

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 reads
wakeup-source from the controller device node. Instead,
serial_core_add_one_port() unconditionally marks the child tty device as
wakeup-capable:

  tty_dev = tty_port_register_device_attr_serdev(port, drv->tty_driver,
                  uport->line, uport->dev, &uport->port_dev->dev, port,
                  uport->tty_groups);
  if (!IS_ERR(tty_dev)) {
          device_set_wakeup_capable(tty_dev, 1);
  }

And lpuart_uport_is_active() in drivers/tty/serial/fsl_lpuart.c checks
wakeup state on that child tty_dev (configured via sysfs) rather than the
platform device:

  tty = tty_port_tty_get(port);
  if (tty) {
          tty_dev = tty->dev;
          may_wake = tty_dev && device_may_wakeup(tty_dev);
          tty_kref_put(tty);
  }

Should fsl-lpuart.yaml and the driver be updated to support wakeup-source
before adding this property to the devicetree?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1793645417.git.stefano.r@variscite.com?part=1

  reply	other threads:[~2026-11-02 19:03 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 [this message]
2026-11-02 18:55 ` [PATCH v1 2/2] arm64: dts: imx93-var-som-symphony: " Stefano Radaelli
2026-11-02 19:04   ` sashiko-bot

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-193978@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