From: Frank Li <Frank.li@nxp.com>
To: Ernest Van Hoecke <ernestvanhoecke@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Ernest Van Hoecke <ernest.vanhoecke@toradex.com>,
Emanuele Ghidoli <emanuele.ghidoli@toradex.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v2 1/6] dt-bindings: arm: fsl: add Verdin iMX95
Date: Tue, 24 Mar 2026 12:08:09 -0400 [thread overview]
Message-ID: <acK26Vt_rasid8AR@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260313-verdin-imx95-upstream-frank-li-base-v2-1-bd488be7c699@toradex.com>
On Fri, Mar 13, 2026 at 09:57:42AM +0100, Ernest Van Hoecke wrote:
> From: Ernest Van Hoecke <ernest.vanhoecke@toradex.com>
>
> Add DT compatible strings for the Verdin i.MX95 SoM and its supported
> carrier boards: the Verdin Development Board, and the Dahlia, Ivy,
> Mallow and Yavia carrier boards.
>
> Link: https://www.toradex.com/computer-on-modules/verdin-arm-family/nxp-imx95
> Link: https://www.toradex.com/products/carrier-board/verdin-development-board-kit
> Link: https://www.toradex.com/products/carrier-board/dahlia-carrier-board-kit
> Link: https://www.toradex.com/products/carrier-board/ivy-carrier-board
> Link: https://www.toradex.com/products/carrier-board/mallow-carrier-board
> Link: https://www.toradex.com/products/carrier-board/yavia
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> Signed-off-by: Ernest Van Hoecke <ernest.vanhoecke@toradex.com>
> ---
can you rebase to https://git.kernel.org/pub/scm/linux/kernel/git/frank.li/linux.git/log/?h=for-next
Frank
> v2: Added Krzysztof's reviewed-by
> v1: https://lore.kernel.org/all/20260305-verdin-imx95-upstream-frank-li-base-v1-1-823fad02def9@toradex.com/
> ---
> Documentation/devicetree/bindings/arm/fsl.yaml | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml
> index 5716d701292c..f0701143b237 100644
> --- a/Documentation/devicetree/bindings/arm/fsl.yaml
> +++ b/Documentation/devicetree/bindings/arm/fsl.yaml
> @@ -1477,6 +1477,30 @@ properties:
> - const: toradex,smarc-imx95 # Toradex SMARC iMX95 Module
> - const: fsl,imx95
>
> + - description: Toradex Boards with Verdin iMX95 Modules
> + items:
> + - enum:
> + - toradex,verdin-imx95-nonwifi-dahlia # Verdin iMX95 Module on Dahlia
> + - toradex,verdin-imx95-nonwifi-dev # Verdin iMX95 Module on Verdin Development Board
> + - toradex,verdin-imx95-nonwifi-ivy # Verdin iMX95 Module on Ivy
> + - toradex,verdin-imx95-nonwifi-mallow # Verdin iMX95 Module on Mallow
> + - toradex,verdin-imx95-nonwifi-yavia # Verdin iMX95 Module on Yavia
> + - const: toradex,verdin-imx95-nonwifi # Verdin iMX95 Module without Wi-Fi / BT
> + - const: toradex,verdin-imx95 # Verdin iMX95 Module
> + - const: fsl,imx95
> +
> + - description: Toradex Boards with Verdin iMX95 Wi-Fi / BT Modules
> + items:
> + - enum:
> + - toradex,verdin-imx95-wifi-dahlia # Verdin iMX95 Wi-Fi / BT Module on Dahlia
> + - toradex,verdin-imx95-wifi-dev # Verdin iMX95 Wi-Fi / BT Module on Verdin Development B.
> + - toradex,verdin-imx95-wifi-ivy # Verdin iMX95 Wi-Fi / BT Module on Ivy
> + - toradex,verdin-imx95-wifi-mallow # Verdin iMX95 Wi-Fi / BT Module on Mallow
> + - toradex,verdin-imx95-wifi-yavia # Verdin iMX95 Wi-Fi / BT Module on Yavia
> + - const: toradex,verdin-imx95-wifi # Verdin iMX95 Wi-Fi / BT Module
> + - const: toradex,verdin-imx95 # Verdin iMX95 Module
> + - const: fsl,imx95
> +
> - description: i.MXRT1050 based Boards
> items:
> - enum:
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-03-24 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 8:57 [PATCH v2 0/6] arm64: dts: freescale: add Verdin iMX95 Ernest Van Hoecke
2026-03-13 8:57 ` [PATCH v2 1/6] dt-bindings: arm: fsl: " Ernest Van Hoecke
2026-03-24 16:08 ` Frank Li [this message]
2026-03-13 8:57 ` [PATCH v2 2/6] arm64: dts: freescale: Add Verdin iMX95 support Ernest Van Hoecke
2026-03-24 16:14 ` Frank Li
2026-03-25 11:27 ` Francesco Dolcini
2026-03-25 15:01 ` Frank Li
2026-03-13 8:57 ` [PATCH v2 3/6] arm64: dts: freescale: imx95-verdin: Add Dahlia carrier board Ernest Van Hoecke
2026-03-13 8:57 ` [PATCH v2 4/6] arm64: dts: freescale: imx95-verdin: Add Ivy " Ernest Van Hoecke
2026-03-13 8:57 ` [PATCH v2 5/6] arm64: dts: freescale: imx95-verdin: Add Mallow " Ernest Van Hoecke
2026-03-13 8:57 ` [PATCH v2 6/6] arm64: dts: freescale: imx95-verdin: Add Yavia " Ernest Van Hoecke
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=acK26Vt_rasid8AR@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emanuele.ghidoli@toradex.com \
--cc=ernest.vanhoecke@toradex.com \
--cc=ernestvanhoecke@gmail.com \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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