Linux kernel and device drivers for NXP i.MX platforms
 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 3/3] arm64: dts: imx8mp-var-smarc: Add support for Variscite Echo board
Date: Tue, 10 Nov 2026 18:41:03 +0000	[thread overview]
Message-ID: <sashiko-outbox-207596@kernel.org> (raw)
In-Reply-To: <3cb427c8d5c6244cebeca5310bd03171f5685edf.1794334398.git.stefano.r@variscite.com>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] arm64: dts: imx8mp-var-smarc-echo: missing uart-has-rtscts on
  uart1
--

commit 2120b57aa36b03b0bbf74c4c8b3c605d83172578
Author: Stefano Radaelli <stefano.r@variscite.com>

arm64: dts: imx8mp-var-smarc: Add support for Variscite Echo board

This commit adds a device tree for the Variscite Echo carrier board paired
with the VAR-SMARC-MX8M-PLUS system on module.

Link: https://variscite.com/carrier-boards/echo-board/

> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-var-smarc-echo.dts b/arch/arm64/boot/dts/freescale/imx8mp-var-smarc-echo.dts
> new file mode 100644
> index 0000000000000..341d8af16cd82
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/imx8mp-var-smarc-echo.dts

[ ... ]

> +/* Header */
> +&uart1 {
> +	pinctrl-names = "default";
> +	pinctrl-0 = <&pinctrl_uart1>;
> +	status = "okay";
> +};

[Severity: Medium]
Should the uart1 node include uart-has-rtscts?

pinctrl_uart1 muxes MX8MP_IOMUXC_UART3_RXD__UART1_DCE_CTS and
MX8MP_IOMUXC_UART3_TXD__UART1_DCE_RTS, but without uart-has-rtscts on
the node, imx_uart_probe() leaves sport->have_rtscts false.  As a result,
imx_uart_set_termios() clears CRTSCTS and imx_uart_startup() ignores the
RTS pin, leaving hardware flow control and RS485 unusable on uart1.

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

      parent reply	other threads:[~2026-11-10 18:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 18:18 [PATCH v1 0/3] Add support for Variscite VAR-SMARC-MX8M-PLUS and Echo board Stefano Radaelli
2026-11-10 18:18 ` [PATCH v1 1/3] dt-bindings: arm: fsl: Add Variscite VAR-SMARC-MX8M Plus Stefano Radaelli
2026-11-10 18:18 ` [PATCH v1 2/3] arm64: dts: freescale: Add support for Variscite VAR-SMARC-MX8M-PLUS Stefano Radaelli
2026-11-10 18:50   ` sashiko-bot
2026-11-10 18:18 ` [PATCH v1 3/3] arm64: dts: imx8mp-var-smarc: Add support for Variscite Echo board Stefano Radaelli
2026-11-10 18:39   ` Fabio Estevam
2026-11-10 18:41   ` 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-207596@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