All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Stefano Radaelli" <stefano.radaelli21@gmail.com>
Cc: Frank.Li@kernel.org, imx@lists.linux.dev, conor+dt@kernel.org,
	robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v1 07/15] arm64: dts: freescale: imx8mn-var-som: Rework WiFi/BT and add legacy dts
Date: Fri, 03 Jul 2026 08:57:38 +0000	[thread overview]
Message-ID: <20260703085738.BFE0D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <541308c48bdc3b6860ce25027ed1a01e38aa2971.1783067947.git.stefano.r@variscite.com>

Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [High] The removal of the Broadcom WiFi node from `imx8mn-var-som.dtsi` silently breaks WiFi support on the downstream imx8mn-rve-gateway board.
- [Medium] Incomplete reversion of IW61x pinmux changes in the legacy device tree.
- [Low] Unnecessary `#address-cells` and `#size-cells` properties are left in `usdhc1`, which will trigger dtc warnings for boards without a WiFi child node.
--

commit 5a726be8cbb43e633eba48d88581647aae4f82ba
Author: Stefano Radaelli <stefano.r@variscite.com>

arm64: dts: freescale: imx8mn-var-som: Rework WiFi/BT and add legacy dts

The VAR-SOM-MX8MN currently integrates the NXP IW61x wireless module,
providing WiFi over SDIO and Bluetooth over UART.

Move the wireless module configuration out of the base
imx8mn-var-som.dtsi and provide dedicated variant includes.

> diff --git a/arch/arm64/boot/dts/freescale/imx8mn-var-som-symphony-legacy.dts b/arch/arm64/boot/dts/freescale/imx8mn-var-som-symphony-legacy.dts
> new file mode 100644
> index 0000000000000..5998ebcef4740
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/imx8mn-var-som-symphony-legacy.dts
> @@ -0,0 +1,19 @@
[ ... ]
> +&bluetooth_iw61x {
> +	status = "disabled";
> +};
> +
> +&iw61x_pwrseq {
> +	status = "disabled";
> +};
> +
> +&usdhc1 {
> +	/delete-property/ mmc-pwrseq;
> +};

[Severity: Medium]
Does this leave unintended pin configurations active for the legacy board?

Since this file includes imx8mn-var-som-symphony.dts, it inherits the
pinctrl properties from imx8mn-var-som-wifi-bt-iw61x.dtsi:

&usdhc1 {
	pinctrl-0 = <&pinctrl_usdhc1>, <&pinctrl_wifi>;
	pinctrl-1 = <&pinctrl_usdhc1_100mhz>, <&pinctrl_wifi>;
	pinctrl-2 = <&pinctrl_usdhc1_200mhz>, <&pinctrl_wifi>;
};

Should this legacy file also override the pinctrl properties to remove
<&pinctrl_wifi> and <&pinctrl_bt> from usdhc1 and uart2 to prevent
hardware conflicts on GPIO2_IO6, GPIO2_IO10, and GPIO2_IO20?

> diff --git a/arch/arm64/boot/dts/freescale/imx8mn-var-som.dtsi b/arch/arm64/boot/dts/freescale/imx8mn-var-som.dtsi
> index ac22dd3e65421..ff5f658b33ded 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mn-var-som.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8mn-var-som.dtsi
> @@ -371,7 +371,6 @@ &usbotg1 {
>  	status = "okay";
>  };
>  
> -/* WIFI */
>  &usdhc1 {
>  	#address-cells = <1>;
>  	#size-cells = <0>;

[Severity: Low]
Will leaving these properties here trigger avoid_unnecessary_addr_size dtc
warnings for boards without a WiFi child node?

Since the wifi@1 child node is removed below, usdhc1 no longer has any child
nodes for boards using the new IW61x module.

> @@ -383,11 +382,6 @@ &usdhc1 {
>  	non-removable;
>  	keep-power-in-suspend;
>  	status = "okay";
> -
> -	brcmf: wifi@1 {
> -		reg = <1>;
> -		compatible = "brcm,bcm4329-fmac";
> -	};
>  };

[Severity: High]
Does removing the Broadcom WiFi node from the shared SOM dtsi silently break
WiFi support on downstream carrier boards?

Looking at arch/arm64/boot/dts/freescale/imx8mn-rve-gateway.dts, it includes
imx8mn-var-som.dtsi but was not updated to include a Wi-Fi variant include. 
Will the brcmfmac driver fail to bind to the device tree node for the gateway
board, breaking DT-dependent configurations?

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

  reply	other threads:[~2026-07-03  8:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03  8:45 [PATCH v1 00/15] arm64: dts: freescale: imx8mn-var-som: Align SOM and Symphony DTSs Stefano Radaelli
2026-07-03  8:45 ` [PATCH v1 01/15] arm64: dts: freescale: imx8mn-var-som: Move UART4 description to Symphony Stefano Radaelli
2026-07-03  8:45 ` [PATCH v1 02/15] arm64: dts: freescale: imx8mn-var-som: move SD card support " Stefano Radaelli
2026-07-03  8:54   ` sashiko-bot
2026-07-03  8:45 ` [PATCH v1 03/15] arm64: dts: freescale: imx8mn-var-som: Align fsl,pins tables Stefano Radaelli
2026-07-03  8:45 ` [PATCH v1 04/15] arm64: dts: freescale: imx8mn-var-som: Update FEC support with MaxLinear PHY Stefano Radaelli
2026-07-03  9:01   ` sashiko-bot
2026-07-03  8:45 ` [PATCH v1 05/15] arm64: dts: freescale: imx8mn-var-som: Add support for WM8904 audio codec Stefano Radaelli
2026-07-03  8:55   ` sashiko-bot
2026-07-03  8:45 ` [PATCH v1 06/15] arm64: dts: freescale: imx8mn-var-som: Add MCP251xFD CAN controller Stefano Radaelli
2026-07-03  8:45 ` [PATCH v1 07/15] arm64: dts: freescale: imx8mn-var-som: Rework WiFi/BT and add legacy dts Stefano Radaelli
2026-07-03  8:57   ` sashiko-bot [this message]
2026-07-03  8:45 ` [PATCH v1 08/15] arm64: dts: freescale: imx8mn-var-som: drop duplicate USB OTG node Stefano Radaelli
2026-07-03  8:45 ` [PATCH v1 09/15] arm64: dts: freescale: imx8mn-var-som: enable FlexSPI interface Stefano Radaelli
2026-07-03  8:56   ` sashiko-bot
2026-07-03  8:45 ` [PATCH v1 10/15] arm64: dts: imx8mn-var-som-symphony: Add TPM2 support Stefano Radaelli
2026-07-03  9:00   ` sashiko-bot
2026-07-03  8:45 ` [PATCH v1 11/15] arm64: dts: imx8mn-var-som-symphony: Enable I2C4 Stefano Radaelli
2026-07-03  8:45 ` [PATCH v1 12/15] arm64: dts: imx8mn-var-som-symphony: add wakeup sources Stefano Radaelli
2026-07-03  8:46 ` [PATCH v1 13/15] arm64: dts: imx8mn-var-som-symphony: keep RGB_SEL low Stefano Radaelli
2026-07-03  8:46 ` [PATCH v1 14/15] arm64: dts: imx8mn-var-som-symphony: enable PWM1 Stefano Radaelli
2026-07-03  8:46 ` [PATCH v1 15/15] arm64: dts: imx8mn-var-som-symphony: Disable internal RTC Stefano Radaelli

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=20260703085738.BFE0D1F000E9@smtp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.