Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Joseph Guo <qijian.guo@nxp.com>
To: sashiko-reviews@lists.linux.dev
Cc: Frank.Li@kernel.org, imx@lists.linux.dev, conor+dt@kernel.org,
	robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [EXT] Re: [PATCH v2 1/3] arm64: dts: imx93-11x11-frdm: factor out common parts into dtsi
Date: Mon, 3 Aug 2026 17:09:10 +0800	[thread overview]
Message-ID: <391bab14-cedd-47be-8db7-4fc59da8f467@nxp.com> (raw)
In-Reply-To: <20260723072206.E92621F000E9@smtp.kernel.org>

On 7/23/2026 3:22 PM, sashiko-bot@kernel.org wrote:
> Caution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report this email' button
> 
> 
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The patch contradicts its v2 changelog by moving the board-specific `lpuart5` pin assignments into the common `.dtsi` file instead of the board-specific `.dts`.
> --
> 
> --- Patch [1]: [PATCH v2 1/3] arm64: dts: imx93-11x11-frdm: factor out common parts into dtsi ---
> commit 35cb24d7221e1d0efbc151d7ebfd44422372ffdb
> Author: Joseph Guo <qijian.guo@nxp.com>
> 
> arm64: dts: imx93-11x11-frdm: factor out common parts into dtsi
> 
> This commit extracts common hardware definitions from the i.MX93 FRDM board
> into a shared imx93-11x11-frdm-common.dtsi file to allow reuse by the Wireless
> FRDM board. The FRDM-IMX93 board-specific .dts is updated to include the
> common dtsi.
> 
>> ---
>> Changes in v2:
>> - Move board specific lpuart5 pin assignment to board dts.
>> - Move pcal6408 node to board dts
>> ---
>>  ...11x11-frdm.dts => imx93-11x11-frdm-common.dtsi} | 129 +---
>>  arch/arm64/boot/dts/freescale/imx93-11x11-frdm.dts | 679 +--------------------
>>  2 files changed, 7 insertions(+), 801 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/freescale/imx93-11x11-frdm-common.dtsi b/arch/arm64/boot/dts/freescale/imx93-11x11-frdm-common.dtsi
>> new file mode 100644
>> index 0000000000000..5c8fdd77ec15b
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/freescale/imx93-11x11-frdm-common.dtsi
> [ ... ]
>> +&lpuart5 {
>> +     pinctrl-0 = <&pinctrl_uart5>;
>> +     pinctrl-names = "default";
>> +     status = "okay";
> 
> [Severity: Medium]
> Does this contradict the v2 changelog?
> 
> The changelog states "Move board specific lpuart5 pin assignment to board
> dts", but the lpuart5 node and its pinctrl assignment are being added to the
> common imx93-11x11-frdm-common.dtsi file here.
> 

The pinctrl for uart5 is same on imx93w-frdm and imx93-11x11-frdm. The difference are the reset/wakeup gpio and vcc-supply.
> [ ... ]
>> +     pinctrl_uart5: uart5grp {
>> +             fsl,pins = <
>> +                     MX93_PAD_DAP_TDO_TRACESWO__LPUART5_TX           0x31e
>> +                     MX93_PAD_DAP_TDI__LPUART5_RX                    0x31e
>> +                     MX93_PAD_DAP_TMS_SWDIO__LPUART5_RTS_B           0x31e
>> +                     MX93_PAD_DAP_TCLK_SWCLK__LPUART5_CTS_B          0x31e
>> +             >;
>> +     };
> 
> [Severity: Medium]
> Similarly, the pinctrl_uart5 pinmux group definition is placed in the
> common file instead of the board-specific dts.
> 
> Could this incorrectly share board-specific pin muxing with other boards that
> include this dtsi?
> 
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260723-imx93w_frdm-v2-0-b108a76b2e40@nxp.com?part=1

-- 
Best Regards,
Joseph

  reply	other threads:[~2026-08-03  9:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  7:13 [PATCH v2 0/3] Add i.MX93 Wireless FRDM board support Joseph Guo
2026-07-23  7:13 ` [PATCH v2 1/3] arm64: dts: imx93-11x11-frdm: factor out common parts into dtsi Joseph Guo
2026-07-23  7:22   ` sashiko-bot
2026-08-03  9:09     ` Joseph Guo [this message]
2026-07-23  7:13 ` [PATCH v2 2/3] dt-bindings: arm: fsl: Add i.MX93 Wireless FRDM board Joseph Guo
2026-07-23  7:13 ` [PATCH v2 3/3] arm64: dts: imx93: Add i.MX93 Wireless FRDM board support Joseph Guo
2026-07-23  7:25   ` sashiko-bot
2026-08-06 19:48 ` [PATCH v2 0/3] " Frank.Li

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=391bab14-cedd-47be-8db7-4fc59da8f467@nxp.com \
    --to=qijian.guo@nxp.com \
    --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 \
    /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