From: sashiko-bot@kernel.org
To: "Chancel Liu" <chancel.liu@oss.nxp.com>
Cc: imx@lists.linux.dev, conor+dt@kernel.org, Frank.Li@kernel.org,
devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 16/17] arm64: dts: imx952-evk: Add pinmux and mark conflicting devices for MQS1
Date: Fri, 14 Aug 2026 07:42:24 +0000 [thread overview]
Message-ID: <20260814074228.89E871F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260814072022.4064009-17-chancel.liu@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch silently modifies the `&sai1` node to append SoC-level clock definitions (`pll8k` and `pll11k`) in a board-specific `.dts` file, violating Devicetree abstractions and the commit message's stated scope.
--
--- Patch [16]: [PATCH 16/17] arm64: dts: imx952-evk: Add pinmux and mark conflicting devices for MQS1 ---
commit 8ad36d874036617823df79dfb507cb8569fd6f0b
Author: Chancel Liu <chancel.liu@nxp.com>
arm64: dts: imx952-evk: Add pinmux and mark conflicting devices for MQS1
This commit adds the MQS1 pinctrl group and labels the conflicting device and
sound card so the shared imx9-mqs overlay can disable them.
> diff --git a/arch/arm64/boot/dts/freescale/imx952-evk.dts b/arch/arm64/boot/dts/freescale/imx952-evk.dts
> index e9d735dc2a51b..522c6cb9abf28 100644
> --- a/arch/arm64/boot/dts/freescale/imx952-evk.dts
> +++ b/arch/arm64/boot/dts/freescale/imx952-evk.dts
[ ... ]
> @@ -519,11 +519,21 @@ &micfil {
> status = "okay";
> };
>
> +&mqs1 {
> + pinctrl-0 = <&pinctrl_mqs1>, <&mqs1_enable>;
> + pinctrl-names = "default";
> +};
> +
> &mu7 {
> status = "okay";
> };
>
> &sai1 {
> + clocks = <&scmi_clk IMX952_CLK_BUSAON>, <&clk_dummy>,
> + <&scmi_clk IMX952_CLK_SAI1>, <&clk_dummy>,
> + <&clk_dummy>, <&scmi_clk IMX952_CLK_AUDIOPLL1>,
> + <&scmi_clk IMX952_CLK_AUDIOPLL2>;
> + clock-names = "bus", "mclk0", "mclk1", "mclk2", "mclk3", "pll8k", "pll11k";
[Severity: Medium]
Is it intentional to place these SoC-level clock definitions in the
board-specific .dts file rather than the base SoC .dtsi file?
The added clocks (IMX952_CLK_AUDIOPLL1 and IMX952_CLK_AUDIOPLL2) appear to be
internal SoC clocks. Wiring these to the sai1 peripheral seems like an
SoC-level integration detail, and placing it here might force other boards
using sai1 to duplicate this wiring.
Additionally, this change is not mentioned in the commit message. Could the
commit message be updated to document this, or should this modification be
split into a separate patch?
> assigned-clocks = <&scmi_clk IMX952_CLK_AUDIOPLL1_VCO>,
> <&scmi_clk IMX952_CLK_AUDIOPLL2_VCO>,
> <&scmi_clk IMX952_CLK_AUDIOPLL1>,
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260814072022.4064009-1-chancel.liu@oss.nxp.com?part=16
next prev parent reply other threads:[~2026-08-14 7:42 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
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 [this message]
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=20260814074228.89E871F000E9@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