linux-kernel - RE: [PATCH 2/2] arch: arm64: imx93-wevk: Add i.MX93W EVK board support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
 <VI0PR04MB121141B628431B6CAAC3A029F9296A@VI0PR04MB12114.eurprd04.prod.outlook.com>
Date: Wed, 21 Jan 2026 06:41:48 +0000
From: Sherry Sun <sherry.sun@....com>
To: Frank Li <frank.li@....com>
CC: "robh@...nel.org" <robh@...nel.org>, "krzk+dt@...nel.org"
	<krzk+dt@...nel.org>, "conor+dt@...nel.org" <conor+dt@...nel.org>,
	"shawnguo@...nel.org" <shawnguo@...nel.org>, Daniel Baluta
	<daniel.baluta@....com>, "dario.binacchi@...rulasolutions.com"
	<dario.binacchi@...rulasolutions.com>, "alexander.stein@...tq-group.com"
	<alexander.stein@...tq-group.com>, "Markus.Niebel@...group.com"
	<Markus.Niebel@...group.com>, "matthias.schiffer@...group.com"
	<matthias.schiffer@...group.com>, "y.moog@...tec.de" <y.moog@...tec.de>,
	"josua@...id-run.com" <josua@...id-run.com>, Francesco Dolcini
	<francesco.dolcini@...adex.com>, "primoz.fiser@...ik.com"
	<primoz.fiser@...ik.com>, "s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
	"festevam@...il.com" <festevam@...il.com>, "devicetree@...r.kernel.org"
	<devicetree@...r.kernel.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "imx@...ts.linux.dev" <imx@...ts.linux.dev>,
	"linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "kernel@...gutronix.de"
	<kernel@...gutronix.de>
Subject: RE: [PATCH 2/2] arch: arm64: imx93-wevk: Add i.MX93W EVK board
 support



> Subject: Re: [PATCH 2/2] arch: arm64: imx93-wevk: Add i.MX93W EVK board
> support
> 
> On Tue, Jan 20, 2026 at 06:26:04PM +0800, Sherry Sun wrote:
> > i.MX93W SiP is created by integrating i.MX93 and IW610 WLCSP (Wi-Fi +
> > BLE + 802.15.4). And i.MX93W EVK board with the i.MX93W SiP basically
> > reuse the i.MX93 11x11 EVK board, with some minor functional and pin
> > connection differences.
> >
> > Here are the detailed differences between i.MX93W EVK and i.MX93 11x11
> > EVK board.
> >
> > Function differences:
> > Function	i.MX93W EVK			i.MX93 EVK
> > WIFI/BT		IW610 in i.MX93W		IW612 M.2 module
> > MQS		N				Y
> > PDM MIC		N				Y
> > M.2		N				Y
> > RPi 40-pin HDR	Limited support(pin conflict) 	Y
> >
> > Pin connection differences:
> > Function  Signal name	i.MX93W EVK		i.MX93 EVK
> > WIFI/BT	  SPI_FRM	SAI1_TXFS (spi1.PCS0)	GPIO_IO08
> (spi3.PCS0)
> > 	  SPI_TXD	SAI1_TXC (spi1.SIN)	GPIO_IO09 (spi3.SIN)
> > 	  SPI_RXD	SAI1_RXD0 (spi1.SOUT)	GPIO_IO10 (spi3.SOUT)
> > 	  SPI_CLK	SAI1_TXD0 (spi1.SCK)	GPIO_IO11 (spi3.SCK)
> > 	  SPI_INT	CCM_CLKO1		on-board IO expander
> > 	  NB_WAKE_IN	PDM_CLK			on-module IO
> expander
> > 	  WL_WAKE_IN	PDM_BIT_STREAM0		on-module IO
> expander
> > 	  IND_RST_WL	PDM_BIT_STREAM1		on-module IO
> expander
> > 	  IND_RST_NB	GPIO_IO28		on-module IO expander
> > 	  PDn		GPIO_IO29		on-module IO expander
> > 	  NB_WAKE_OUT	GPIO_IO14		on-board IO
> expander
> > 	  WL_WAKE_OUT	GPIO_IO15		CCM_CLKO1
> > I2C3	  I2C3_SDA	GPIO_IO00		GPIO_IO28
> > 	  I2C3_SCL	GPIO_IO01		GPIO_IO29
> >
> > Signed-off-by: Sherry Sun <sherry.sun@....com>
> > ---
> >  arch/arm64/boot/dts/freescale/Makefile       |  1 +
> >  arch/arm64/boot/dts/freescale/imx93w-evk.dts | 73
> > ++++++++++++++++++++
> >  2 files changed, 74 insertions(+)
> >  create mode 100644 arch/arm64/boot/dts/freescale/imx93w-evk.dts
> >
> > diff --git a/arch/arm64/boot/dts/freescale/Makefile
> > b/arch/arm64/boot/dts/freescale/Makefile
> > index ce8f937c2315..5cb1b1d8499f 100644
> > --- a/arch/arm64/boot/dts/freescale/Makefile
> > +++ b/arch/arm64/boot/dts/freescale/Makefile
> > @@ -399,6 +399,7 @@ dtb-$(CONFIG_ARCH_MXC) += imx93-9x9-qsb-
> i3c.dtb
> >  dtb-$(CONFIG_ARCH_MXC) += imx93-11x11-evk.dtb
> >  dtb-$(CONFIG_ARCH_MXC) += imx93-11x11-frdm.dtb
> >  dtb-$(CONFIG_ARCH_MXC) += imx93-14x14-evk.dtb
> > +dtb-$(CONFIG_ARCH_MXC) += imx93w-evk.dtb
> >  dtb-$(CONFIG_ARCH_MXC) += imx93-kontron-bl-osm-s.dtb
> >  dtb-$(CONFIG_ARCH_MXC) += imx93-phyboard-nash.dtb
> >  dtb-$(CONFIG_ARCH_MXC) += imx93-phyboard-segin.dtb diff --git
> > a/arch/arm64/boot/dts/freescale/imx93w-evk.dts
> > b/arch/arm64/boot/dts/freescale/imx93w-evk.dts
> > new file mode 100644
> > index 000000000000..c2c758b7f9a4
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/freescale/imx93w-evk.dts
> 
> Is it possible to use overlay file?

Hi Frank,

Thanks for the suggestion, after checking, I prefer to use dts for
imx93w-evk for below two main reasons:
1. The i.MX93W EVK (with the i.MX93W SiP) has a fixed hardware
configuration, so using a DTSO seems doesn't provide clear
advantages in this case. A regular DTS is simpler and more appropriate
for a static board design.
2. DTSO doesn't support /delete-node/ and /delete-property/, both
of which are used in this device tree. Handling such modifications is
more straightforward when using a normal DTS rather than an overlay.

Best Regards
Sherry

> 
> Frank
> 
> > @@ -0,0 +1,73 @@
> > +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> > +/*
> > + * Copyright 2026 NXP
> > + */
> > +
> > +#include "imx93-11x11-evk.dts"
> > +
> > +/ {
> > +	model = "NXP i.MX93W EVK board";
> > +	compatible = "fsl,imx93w-evk", "fsl,imx93";
> > +
> > +	/delete-node/ regulator-m2-pwr;
> > +
> > +	sound-bt-sco {
> > +		status = "disabled";
> > +	};
> > +
> > +	sound-micfil {
> > +		status = "disabled";
> > +	};
> > +};
> > +
> > +&pcal6524 {
> > +	/delete-node/ m2-pcm-level-shifter-hog; };
> > +
> > +&reg_usdhc3_vmmc {
> > +	/delete-property/ vin-supply;
> > +	pinctrl-0 = <&pinctrl_reg_usdhc3_vmmc>;
> > +	pinctrl-names = "default";
> > +	gpio = <&gpio2 29 GPIO_ACTIVE_HIGH>; };
> > +
> > +&usdhc3_pwrseq {
> > +	pinctrl-0 = <&pinctrl_usdhc3_pwrseq>;
> > +	pinctrl-names = "default";
> > +	reset-gpios = <&gpio1 10 GPIO_ACTIVE_LOW>; };
> > +
> > +&micfil {
> > +	status = "disabled";
> > +};
> > +
> > +&sai1 {
> > +	status = "disabled";
> > +};
> > +
> > +&iomuxc {
> > +	pinctrl_lpi2c3: lpi2c3grp {
> > +		fsl,pins = <
> > +			MX93_PAD_GPIO_IO00__LPI2C3_SDA
> 	0x40000b9e
> > +			MX93_PAD_GPIO_IO01__LPI2C3_SCL
> 	0x40000b9e
> > +		>;
> > +	};
> > +
> > +	pinctrl_reg_usdhc3_vmmc: regusdhc3vmmcgrp {
> > +		fsl,pins = <
> > +			MX93_PAD_GPIO_IO29__GPIO2_IO29
> 	0x31e
> > +		>;
> > +	};
> > +
> > +	pinctrl_usdhc3_pwrseq: usdhc3pwrseqgrp {
> > +		fsl,pins = <
> > +			MX93_PAD_PDM_BIT_STREAM1__GPIO1_IO10
> 	0x31e
> > +		>;
> > +	};
> > +
> > +	pinctrl_usdhc3_wlan: usdhc3wlangrp {
> > +		fsl,pins = <
> > +			MX93_PAD_GPIO_IO15__GPIO2_IO15
> 	0x31e
> > +		>;
> > +	};
> > +};
> > --
> > 2.37.1
> >