From: sashiko-bot@kernel.org
To: "Chancel Liu" <chancel.liu@oss.nxp.com>
Cc: robh@kernel.org, Frank.Li@kernel.org, imx@lists.linux.dev,
conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 06/17] arm64: dts: imx93-14x14-evk: Add board muxes to select between FlexCAN1 and MQS1
Date: Fri, 14 Aug 2026 07:31:36 +0000 [thread overview]
Message-ID: <20260814073137.4C7891F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260814072022.4064009-7-chancel.liu@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incomplete device tree wiring for board muxes. The newly added pinctrl mux states (`can1_fun`, `mqs1_fun`, `mqs1_amp_en`) are defined but never referenced by any consumer device node (such as `flexcan1`), rendering the board mux configuration functionally dead code.
--
--- Patch [6]: [PATCH 06/17] arm64: dts: imx93-14x14-evk: Add board muxes to select between FlexCAN1 and MQS1 ---
commit adc8546ef31dc705c01516aa1b8dc15eb6eaa575
Author: Chancel Liu <chancel.liu@nxp.com>
arm64: dts: imx93-14x14-evk: Add board muxes to select between FlexCAN1 and MQS1
This commit adds GPIO-controlled board muxes to resolve a pin conflict
between FlexCAN1 and MQS1 on the imx93-14x14-evk board. It defines the
mux controllers and their corresponding pinctrl states.
> diff --git a/arch/arm64/boot/dts/freescale/imx93-14x14-evk.dts b/arch/arm64/boot/dts/freescale/imx93-14x14-evk.dts
> index ec78c03f4788b..502237fab3324 100644
> --- a/arch/arm64/boot/dts/freescale/imx93-14x14-evk.dts
> +++ b/arch/arm64/boot/dts/freescale/imx93-14x14-evk.dts
[ ... ]
> + pinctrl-gpiomux {
> + compatible = "pinctrl-multiplexer";
> +
> + can1_fun: can1-grp {
> + mux-states = <&can1_mqs1_mux 0>;
> + };
> +
> + mqs1_amp_en: mqs1-amp-en-grp {
> + mux-states = <&mqs1_amp_en_mux 1>;
> + };
> +
> + mqs1_fun: mqs1-grp {
> + mux-states = <&can1_mqs1_mux 1>;
> + };
> + };
[Severity: Medium]
Are these new pinctrl mux states missing references from their consumer device
nodes?
The can1_fun, mqs1_amp_en, and mqs1_fun states are defined here, but they
don't appear to be referenced by the flexcan1 or mqs1 device nodes.
For example, if the active flexcan1 device node doesn't include <&can1_fun>
in its pinctrl-0 list, won't this configuration remain unapplied and fail to
resolve the hardware routing?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260814072022.4064009-1-chancel.liu@oss.nxp.com?part=6
next prev parent reply other threads:[~2026-08-14 7:31 UTC|newest]
Thread overview: 27+ 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 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 [this message]
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 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=20260814073137.4C7891F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--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