Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@oss.nxp.com>
To: sashiko-reviews@lists.linux.dev
Cc: Chancel Liu <chancel.liu@oss.nxp.com>,
	conor+dt@kernel.org, imx@lists.linux.dev,
	devicetree@vger.kernel.org, Frank.Li@kernel.org, robh@kernel.org
Subject: Re: [PATCH 07/17] arm64: dts: imx93-14x14-evk: Add pinmux and mark conflicting devices for MQS1
Date: Fri, 14 Aug 2026 11:22:33 -0500	[thread overview]
Message-ID: <an9AyQbX8PCl0Cbq@SMW015318> (raw)
In-Reply-To: <20260814073317.E8A691F00A3E@smtp.kernel.org>

On Fri, Aug 14, 2026 at 07:33:12AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The `&flexcan1` node is missing the `<&can1_fun>` pinctrl state to claim the board multiplexer, potentially leaving the physical pins disconnected from the CAN transceiver.
> --
>
> --- Patch [7]: [PATCH 07/17] arm64: dts: imx93-14x14-evk: Add pinmux and mark conflicting devices for MQS1 ---
> commit dcb616d828fd4526406432c88e7ade3c33414225
> Author: Chancel Liu <chancel.liu@nxp.com>
>
> arm64: dts: imx93-14x14-evk: Add pinmux and mark conflicting devices for MQS1
>
> This commit adds the MQS1 pinctrl group and labels conflicting devices
> (BT SCO card and FlexCAN1) so they can be disabled by a shared overlay.
>
> > diff --git a/arch/arm64/boot/dts/freescale/imx93-14x14-evk.dts b/arch/arm64/boot/dts/freescale/imx93-14x14-evk.dts
> > index 502237fab3324..11bb7e52fbb1e 100644
> > --- a/arch/arm64/boot/dts/freescale/imx93-14x14-evk.dts
> > +++ b/arch/arm64/boot/dts/freescale/imx93-14x14-evk.dts
>
> [ ... ]
>
> > @@ -282,7 +282,7 @@ ethphy2: ethernet-phy@2 {
> >  	};
> >  };
> >
> > -&flexcan1 {
> > +mqs1_conflict_dev: &flexcan1 {
> >  	pinctrl-names = "default";
> >  	pinctrl-0 = <&pinctrl_flexcan1>;
>
> [Severity: Medium]
> Is the &can1_fun pinctrl state missing from the pinctrl-0 list here?
>
> If the MQS1 overlay is applied (setting the mux to state 1) and later
> reverted, or if the hardware boots with the multiplexer GPIO high,
> flexcan1 will become active but will fail to assert mux state 0.
>
> Without the &can1_fun reference to claim the board multiplexer, the
> physical pins may remain disconnected from the CAN transceiver, causing it
> to silently fail to communicate on the bus.

Make sense.

Frank

>
> >  	xceiver-supply = <&reg_can1_stby>;
> >  	status = "okay";
> >  };
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260814072022.4064009-1-chancel.liu@oss.nxp.com?part=7

  reply	other threads:[~2026-08-14 16:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  7:20 [PATCH 00/17] arm64: dts: Add MQS1 sound card support for i.MX9 EVK platforms Chancel Liu
2026-08-14  7:20 ` [PATCH 01/17] arm64: dts: imx91_93_common: Add clock and sound-dai-cells properties for MQS Chancel Liu
2026-08-14  7:30   ` sashiko-bot
2026-08-14  7:20 ` [PATCH 02/17] arm64: dts: imx91-11x11-evk: Add board muxes to select between PDM and MQS1 Chancel Liu
2026-08-14  7:20 ` [PATCH 03/17] arm64: dts: imx91-11x11-evk: Add pinmux and mark conflicting devices for MQS1 Chancel Liu
2026-08-14  7:31   ` sashiko-bot
2026-08-14 16:20     ` Frank Li
2026-08-14  7:20 ` [PATCH 04/17] arm64: dts: imx93-11x11-evk: Add board muxes to select between PDM and MQS1 Chancel Liu
2026-08-14  7:20 ` [PATCH 05/17] arm64: dts: imx93-11x11-evk: Add pinmux and mark conflicting devices for MQS1 Chancel Liu
2026-08-14  7:33   ` sashiko-bot
2026-08-14  7:20 ` [PATCH 06/17] arm64: dts: imx93-14x14-evk: Add board muxes to select between FlexCAN1 and MQS1 Chancel Liu
2026-08-14  7:31   ` sashiko-bot
2026-08-14  7:20 ` [PATCH 07/17] arm64: dts: imx93-14x14-evk: Add pinmux and mark conflicting devices for MQS1 Chancel Liu
2026-08-14  7:33   ` sashiko-bot
2026-08-14 16:22     ` Frank Li [this message]
2026-08-14  7:20 ` [PATCH 08/17] arm64: dts: imx94: Add clock and sound-dai-cells properties " Chancel Liu
2026-08-14  7:20 ` [PATCH 09/17] arm64: dts: imx943-evk: Add board muxes to select between CAN1/PDM and MQS1/MIC Chancel Liu
2026-08-14  7:20 ` [PATCH 10/17] arm64: dts: imx943-evk: Add pinmux and mark conflicting devices for MQS1 Chancel Liu
2026-08-14  7:20 ` [PATCH 11/17] arm64: dts: imx95: Add clock and sound-dai-cells properties " Chancel Liu
2026-08-14  7:30   ` sashiko-bot
2026-08-14  7:20 ` [PATCH 12/17] arm64: dts: imx95-15x15-evk: Add board muxes to select between PDM and MQS1 Chancel Liu
2026-08-14  7:20 ` [PATCH 13/17] arm64: dts: imx95-15x15-evk: Add pinmux and mark conflicting devices for MQS1 Chancel Liu
2026-08-14  7:36   ` sashiko-bot
2026-08-14  7:20 ` [PATCH 14/17] arm64: dts: imx952: Add AONMIX MQS device node Chancel Liu
2026-08-14  7:20 ` [PATCH 15/17] arm64: dts: imx952-evk: Add board muxes to select between CAN1/PDM Chancel Liu
2026-08-14  7:20 ` [PATCH 16/17] arm64: dts: imx952-evk: Add pinmux and mark conflicting devices for MQS1 Chancel Liu
2026-08-14  7:42   ` sashiko-bot
2026-08-14  7:20 ` [PATCH 17/17] arm64: dts: fsl: Add DT overlay to build MQS1 sound cards on i.MX9 platforms Chancel Liu
2026-08-14  7:40   ` 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=an9AyQbX8PCl0Cbq@SMW015318 \
    --to=frank.li@oss.nxp.com \
    --cc=Frank.Li@kernel.org \
    --cc=chancel.liu@oss.nxp.com \
    --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