Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Stefano Radaelli" <stefano.radaelli21@gmail.com>
Cc: imx@lists.linux.dev, Frank.Li@kernel.org, robh@kernel.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v1 05/11] ARM: dts: imx6ul: Add Variscite storage and wireless files
Date: Sat, 26 Sep 2026 14:13:33 +0000	[thread overview]
Message-ID: <20260926141333.DF93B1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <778be59a32afc9054147fc40143b502d49d37ffb.1790344389.git.stefano.r@variscite.com>

Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [High] dts: BRCM Wi-Fi fails to enumerate due to missing non-removable property
- [High] dts: IW61X Wi-Fi power enable pin lacks pinctrl configuration
- [Low] dts: unnecessary address and size cells in IW61X usdhc node
--

commit 7bf945c5fafb3aee26ff8892a479bb36b844b74e
Author: Stefano Radaelli <stefano.r@variscite.com>
ARM: dts: imx6ul: Add Variscite storage and wireless files

This patch adds reusable DTSI files for eMMC, NAND, Broadcom Wi-Fi, and
NXP IW61x options on VAR-SOM-6UL and DART-6UL modules. Keeping the module
options independent of the carrier board allows each board DTS to select
its assembled storage and wireless devices.

> diff --git a/arch/arm/boot/dts/nxp/imx/imx6ul-imx6ull-var-dart-wifi-iw61x.dtsi b/arch/arm/boot/dts/nxp/imx/imx6ul-imx6ull-var-dart-wifi-iw61x.dtsi
> new file mode 100644
> index 0000000000000..4d47cea982ec4
> --- /dev/null
> +++ b/arch/arm/boot/dts/nxp/imx/imx6ul-imx6ull-var-dart-wifi-iw61x.dtsi
[ ... ]
> +	iw61x_pwrseq: mmc-pwrseq {
> +		compatible = "mmc-pwrseq-simple";
> +		post-power-on-delay-ms = <100>;
> +		power-off-delay-us = <10000>;
> +		reset-gpios = <&gpio5 6 GPIO_ACTIVE_LOW>, /* WIFI_RESET */
> +			      <&gpio5 2 GPIO_ACTIVE_LOW>; /* WIFI_PWR_EN */
> +	};

[Severity: High]
This references &gpio5 2 as the power enable pin (WIFI_PWR_EN), but is the
corresponding pinmux configuration missing from the pinctrl_wifi group?

Since pinctrl_wifi (defined in imx6ul-var-som.dtsi and imx6ul-var-dart.dtsi)
only configures GPIO5_IO04 and GPIO5_IO06, GPIO5_IO02 appears to be omitted
from the pinmux configuration.

Will this leave the pad in its default hardware reset state, preventing the
GPIO from toggling the Wi-Fi power enable line and leaving the module powered
off?

[ ... ]
> +&usdhc1 {
> +	#address-cells = <1>;
> +	#size-cells = <0>;

[Severity: Low]
Are these address and size cells necessary here?

Unlike the BRCM equivalent which defines a child wifi node, there are no child
nodes under this SDIO controller in the IW61X implementation. Defining address
and size cells without any children will trigger avoid_unnecessary_addr_size
devicetree warnings when compiled with dtc.

> +	pinctrl-names = "default", "state_100mhz", "state_200mhz";
> +	pinctrl-0 = <&pinctrl_usdhc1>, <&pinctrl_wifi>;
[ ... ]
> diff --git a/arch/arm/boot/dts/nxp/imx/imx6ul-imx6ull-var-som-wifi-brcm.dtsi b/arch/arm/boot/dts/nxp/imx/imx6ul-imx6ull-var-som-wifi-brcm.dtsi
> new file mode 100644
> index 0000000000000..d7952233a1ee9
> --- /dev/null
> +++ b/arch/arm/boot/dts/nxp/imx/imx6ul-imx6ull-var-som-wifi-brcm.dtsi
[ ... ]
> +&usdhc1 {
> +	#address-cells = <1>;
> +	#size-cells = <0>;
> +	pinctrl-names = "default", "state_100mhz", "state_200mhz";
> +	pinctrl-0 = <&pinctrl_usdhc1>, <&pinctrl_32k_clk>, <&pinctrl_wifi>;
> +	pinctrl-1 = <&pinctrl_usdhc1_100mhz>, <&pinctrl_32k_clk>, <&pinctrl_wifi>;
> +	pinctrl-2 = <&pinctrl_usdhc1_200mhz>, <&pinctrl_32k_clk>, <&pinctrl_wifi>;
> +	keep-power-in-suspend;
> +	vmmc-supply = <&reg_sd1_vmmc>;
> +	status = "okay";

[Severity: High]
Does this node need the non-removable property to properly enumerate the
Broadcom Wi-Fi module?

Since the module is permanently soldered onto the SOM and does not have a
physical card detect mechanism, omitting non-removable causes the kernel
MMC core to wait indefinitely for a card detect interrupt. Consequently,
the SDIO bus probe might never complete and the Wi-Fi hardware could remain
unusable.

> +
> +	brcmf: wifi@1 {
> +		compatible = "brcm,bcm4329-fmac";
> +		reg = <1>;
> +	};
> +};
[ ... ]

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

  reply	other threads:[~2026-09-26 14:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 14:02 [PATCH v1 00/11] ARM: dts: imx6ul: Add Variscite VAR-SOM-6UL and DART-6UL Stefano Radaelli
2026-09-25 14:02 ` [PATCH v1 01/11] dt-bindings: arm: fsl: Document Variscite i.MX6UL boards Stefano Radaelli
2026-09-25 14:02 ` [PATCH v1 02/11] dt-bindings: net: micrel: Fix RMII clock select property type Stefano Radaelli
2026-09-26 14:13   ` sashiko-bot
2026-09-25 14:02 ` [PATCH v1 03/11] ARM: dts: imx6ul: Add Variscite SoM and DART base files Stefano Radaelli
2026-09-25 14:02 ` [PATCH v1 04/11] ARM: dts: imx6ul: Add Variscite audio codec files Stefano Radaelli
2026-09-25 14:58   ` Frank Li
2026-09-25 15:57     ` Stefano Radaelli
2026-09-25 16:42       ` Frank Li
2026-09-26  8:40         ` Stefano Radaelli
2026-09-26 14:13   ` sashiko-bot
2026-09-25 14:02 ` [PATCH v1 05/11] ARM: dts: imx6ul: Add Variscite storage and wireless files Stefano Radaelli
2026-09-26 14:13   ` sashiko-bot [this message]
2026-09-25 14:02 ` [PATCH v1 06/11] ARM: dts: imx6ul: Add Variscite carrier board files Stefano Radaelli
2026-09-26 14:13   ` sashiko-bot
2026-09-25 14:02 ` [PATCH v1 07/11] ARM: dts: imx6ul: Reuse Variscite DTSI files for Concerto Stefano Radaelli
2026-09-26 14:13   ` sashiko-bot
2026-09-25 14:02 ` [PATCH v1 08/11] ARM: dts: imx6ul: Add Variscite i.MX6UL board variants Stefano Radaelli
2026-09-25 14:02 ` [PATCH v1 09/11] ARM: dts: imx6ull: Add Variscite i.MX6ULL " Stefano Radaelli
2026-09-26 14:13   ` sashiko-bot
2026-09-25 14:02 ` [PATCH v1 10/11] ARM: dts: imx6ulz: Add Variscite i.MX6ULZ " Stefano Radaelli
2026-09-26 14:13   ` sashiko-bot
2026-09-25 14:02 ` [PATCH v1 11/11] ARM: dts: imx6ul: Enable Variscite i.MX6UL board DTBs 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=20260926141333.DF93B1F000FF@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox