From: Sherry Sun <sherry.sun@nxp.com>
To: Frank.Li@nxp.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, s.hauer@pengutronix.de, festevam@gmail.com,
shawnguo@kernel.org, daniel.baluta@nxp.com,
dario.binacchi@amarulasolutions.com,
alexander.stein@ew.tq-group.com, Markus.Niebel@tq-group.com,
matthias.schiffer@tq-group.com, y.moog@phytec.de,
josua@solid-run.com, francesco.dolcini@toradex.com,
primoz.fiser@norik.com
Cc: imx@lists.linux.dev, kernel@pengutronix.de,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 1/5] dt-bindings: arm: fsl: Add i.MX93 Wireless EVK board
Date: Tue, 3 Feb 2026 16:01:33 +0800 [thread overview]
Message-ID: <20260203080137.1492376-2-sherry.sun@nxp.com> (raw)
In-Reply-To: <20260203080137.1492376-1-sherry.sun@nxp.com>
Add DT compatible string for NXP i.MX93 Wireless EVK board.
i.MX93 Wireless SiP is created by integrating i.MX93 and IW610 WLCSP
(Wi-Fi + BLE + 802.15.4). And i.MX93 Wireless EVK board with the i.MX93
Wireless SiP basically reuse the i.MX93 11x11 EVK board, with some minor
functional and pin connection differences.
Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.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 5716d701292c..df01b928c6c5 100644
--- a/Documentation/devicetree/bindings/arm/fsl.yaml
+++ b/Documentation/devicetree/bindings/arm/fsl.yaml
@@ -1441,6 +1441,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,imx93-wireless-evk # i.MX93 and IW610G WLCSP (Wi-Fi + BLE + 802.15.4) SiP EVK Board
- const: fsl,imx93
- description: i.MX94 based Boards
--
2.37.1
next prev parent reply other threads:[~2026-02-03 8:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 8:01 [PATCH V5 0/5] arm64: dts: imx93: Add i.MX93 Wireless EVK and refactor common parts Sherry Sun
2026-02-03 8:01 ` Sherry Sun [this message]
2026-02-03 8:01 ` [PATCH V5 2/5] arm64: dts: imx93: Rename imx93-11x11-evk.dts to imx93-evk-common.dtsi Sherry Sun
2026-02-03 17:02 ` Frank Li
2026-02-04 1:59 ` Sherry Sun
2026-02-03 8:01 ` [PATCH V5 3/5] arm64: dts: imx93: Move 11x11 EVK specific parts back to imx93-11x11-evk.dts Sherry Sun
2026-02-03 17:06 ` Frank Li
2026-02-04 2:00 ` Sherry Sun
2026-02-03 8:01 ` [PATCH V5 4/5] arm64: dts: imx93: Add imx93w.dtsi for i.MX93 Wireless SiP Sherry Sun
2026-02-03 8:01 ` [PATCH V5 5/5] arm64: dts: imx93: Add i.MX93 Wireless EVK board support Sherry Sun
2026-02-03 17:11 ` Frank Li
2026-02-04 2:02 ` Sherry Sun
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=20260203080137.1492376-2-sherry.sun@nxp.com \
--to=sherry.sun@nxp.com \
--cc=Frank.Li@nxp.com \
--cc=Markus.Niebel@tq-group.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=imx@lists.linux.dev \
--cc=josua@solid-run.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.schiffer@tq-group.com \
--cc=primoz.fiser@norik.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=y.moog@phytec.de \
/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