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:
 <VI0PR04MB121142F03A29796D0204A89809296A@VI0PR04MB12114.eurprd04.prod.outlook.com>
Date: Wed, 21 Jan 2026 10:14:15 +0000
From: Sherry Sun <sherry.sun@....com>
To: Krzysztof Kozlowski <krzk@...nel.org>, 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 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

> Subject: Re: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board
> 
> On 21/01/2026 09:05, Sherry Sun wrote:
> >
> >
> >> Subject: Re: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board
> >>
> >> On 21/01/2026 04:18, Sherry Sun wrote:
> >>>
> >>>
> >>>> Subject: Re: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK
> >>>> board
> >>>>
> >>>> On Tue, Jan 20, 2026 at 06:26:03PM +0800, Sherry Sun wrote:
> >>>>> Add DT compatible string for NXP i.MX93W EVK board.
> >>>>>
> >>>>> Signed-off-by: Sherry Sun <sherry.sun@....com>
> >>>>> ---
> >>>>>  Documentation/devicetree/bindings/arm/fsl.yaml | 1 +
> >>>>>  1 file changed, 1 insertion(+)
> >>>>>
> >>>>> diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml
> >>>> b/Documentation/devicetree/bindings/arm/fsl.yaml
> >>>>> index 93ad6f0027d0..1769f243d70f 100644
> >>>>> --- a/Documentation/devicetree/bindings/arm/fsl.yaml
> >>>>> +++ b/Documentation/devicetree/bindings/arm/fsl.yaml
> >>>>> @@ -1432,6 +1432,7 @@ properties:
> >>>>>                - fsl,imx93-11x11-evk       # i.MX93 11x11 EVK Board
> >>>>>                - fsl,imx93-11x11-frdm      # i.MX93 11x11 FRDM Board
> >>>>>                - fsl,imx93-14x14-evk       # i.MX93 14x14 EVK Board
> >>>>> +              - fsl,imx93w-evk            # i.MX93W EVK Board
> >>>>
> >>>> Is 93w 11x11 or 14x14? can you add suffix to keep align existing one.
> >>>>
> >>>
> >>> Hi Frank,
> >>>
> >>> IMX93W-EVK is the official board name, it basically reuse the
> >>> i.MX93
> >>> 11x11 EVK board, as described in the cover letter and dts patch. I
> >>> prefer to still use this name (imx93w-evk) to keep align with the
> >>> board
> >> official name.
> >> It's second case, previous was frdm, with the same argument. I don't
> >> care what you prefer internally. You must align to upstream and all
> >> NXP boards are called soc-foo. Not socfoo.
> >
> > Hi Krzysztof,
> >
> > The soc name is imx93w, the board is basically reuse the i.MX93 11x11
> > EVK, so do you suggest we name it fsl,imx93w-11x11-evk or fsl,imx93w-evk?
> 
> If SoC is imx93w then your compatible is wrong. It clearly says imx93 (no "w").

Hi  Krzysztof,
Sorry for the confusion (I should add more detailed info in this patch commit message),
Actually i.MX93W SiP is created by integrating i.MX93 and IW610 WLCSP (Wi-Fi + BLE + 802.15.4).
The i.MX93W EVK board with the i.MX93W SiP basically reuse the i.MX93 11x11 EVK board.
I am not sure for this case, should we consider to name the soc as imx93w or imx93?

Best Regards
Sherry

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ