[PATCH 0/2] Add i.MX93W EVK board support

[PATCH 0/2] Add i.MX93W EVK board support

[Sherry Sun]

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.

Add device tree and dt-binding for i.MX93W EVK.

Sherry Sun (2):
  dt-bindings: arm: fsl: Add i.MX93W EVK board
  arch: arm64: imx93-wevk: Add i.MX93W EVK board support

 .../devicetree/bindings/arm/fsl.yaml          |  1 +
 arch/arm64/boot/dts/freescale/Makefile        |  1 +
 arch/arm64/boot/dts/freescale/imx93w-evk.dts  | 73 +++++++++++++++++++
 3 files changed, 75 insertions(+)
 create mode 100644 arch/arm64/boot/dts/freescale/imx93w-evk.dts

-- 
2.37.1

[PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

[Sherry Sun]

Add DT compatible string for NXP i.MX93W EVK board.

Signed-off-by: Sherry Sun <sherry.sun@nxp.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
           - const: fsl,imx93
 
       - description: i.MX94 based Boards
-- 
2.37.1

Re: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

[Frank Li]

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@nxp.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.

Frank

>            - const: fsl,imx93
>
>        - description: i.MX94 based Boards
> --
> 2.37.1
>

RE: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

[Sherry Sun]

> 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@nxp.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. 

Please let me know if there any other concerns. Thanks!

Best Regards
Sherry


> Frank
> 
> >            - const: fsl,imx93
> >
> >        - description: i.MX94 based Boards
> > --
> > 2.37.1
> >

Re: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

[Krzysztof Kozlowski]

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@nxp.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.


Best regards,
Krzysztof

RE: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

[Sherry Sun]

> 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@nxp.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?

Best Regards
Sherry

Re: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

[Daniel Baluta]

<snip>

> > >>> +              - 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?

As per my understanding from Krzysztof comment this should be  fsl,imx93-w-evk.
Like soc-foo not socfoo.

Re: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

[Josua Mayer]

Hi Daniel,

On 21/01/2026 11:51, Daniel Baluta wrote:
> <snip>
>
>>>>>> +              - 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?
> As per my understanding from Krzysztof comment this should be  fsl,imx93-w-evk.
> Like soc-foo not socfoo.
If the soc is "imx93w", the physical size / variant is "11x11" and the 
board is "evk",
then I'd define compatible as "fsl,imx93w-11x11-evk", "fsl,imx93w", 
"fsl,imx93".

RE: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

[Sherry Sun]

> Subject: Re: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board
> 
> Hi Daniel,
> 
> On 21/01/2026 11:51, Daniel Baluta wrote:
> > <snip>
> >
> >>>>>> +              - 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?
> > As per my understanding from Krzysztof comment this should be  fsl,imx93-
> w-evk.
> > Like soc-foo not socfoo.
> If the soc is "imx93w", the physical size / variant is "11x11" and the board is
> "evk", then I'd define compatible as "fsl,imx93w-11x11-evk", "fsl,imx93w",
> "fsl,imx93".

Hi Josua,
Thanks for the suggestion, "fsl,imx93w-11x11-evk", "fsl,imx93w", "fsl,imx93" 
compatible seems more reasonable.

Best Regards
Sherry

Re: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

[Krzysztof Kozlowski]

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@nxp.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").

Best regards,
Krzysztof

RE: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

[Sherry Sun]

> 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@nxp.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

RE: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

[Sherry Sun]

> > 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@nxp.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?
> 
Hi Krzysztof,
After some internal discussion, we feel that using the "fsl,imx93-wireless-evk"
compatible string would be clearer and also better aligned with the naming
convention used on previous NXP boards.
What do you think about this direction?

Best Regards
Sherry

Re: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

[Daniel Baluta]

On Wed, Jan 21, 2026 at 5:25 AM Sherry Sun <sherry.sun@nxp.com> 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@nxp.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.


No matter of what name we decide to use in the end please add this clarification
in the commit message.

Also please add small comment describing what are the major
differences between imx93w and
imx93 11x11 board.

thanks,
Daniel.

RE: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board

[Sherry Sun]

> > > 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@nxp.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.
> 
> 
> No matter of what name we decide to use in the end please add this
> clarification in the commit message.
> 
> Also please add small comment describing what are the major differences
> between imx93w and
> imx93 11x11 board.
> 

Hi Daniel,

Sure, actually I have added the detailed difference info in patch#2, seems I also
need to add these info in this patch to avoid confusion, thanks for the reminder.

Best Regards
Sherry

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

[Sherry Sun]

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@nxp.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
@@ -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

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

[Frank Li]

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@nxp.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?

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
>

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

[Sherry Sun]

> 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@nxp.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
> >