From: Mehmet Fide <mehmet.fide@gmail.com>
To: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Stefan Agner <stefan@agner.ch>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Francesco Dolcini <francesco@dolcini.it>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 3/4] dt-bindings: arm: fsl: add the Colibri VF50 and VF61 on Iris
Date: Mon, 10 Aug 2026 16:20:46 +0200 [thread overview]
Message-ID: <20260810142047.2811230-4-mehmet.fide@gmail.com> (raw)
In-Reply-To: <20260810142047.2811230-1-mehmet.fide@gmail.com>
From: Mehmet Fide <mehmet.fide@screeningeagle.com>
The Vybrid Colibri modules are documented on the evaluation board only.
Add the Iris carrier, as the i.MX Colibri modules already have it.
Signed-off-by: Mehmet Fide <mehmet.fide@screeningeagle.com>
---
Documentation/devicetree/bindings/arm/fsl.yaml | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml b/Documentation/devicetree/bindings/arm/fsl.yaml
index 8687631..d58343f 100644
--- a/Documentation/devicetree/bindings/arm/fsl.yaml
+++ b/Documentation/devicetree/bindings/arm/fsl.yaml
@@ -1711,6 +1711,12 @@ properties:
- const: toradex,vf500-colibri_vf50
- const: fsl,vf500
+ - description: Toradex Colibri VF50 Module on Iris Carrier Board
+ items:
+ - const: toradex,vf500-colibri_vf50-on-iris
+ - const: toradex,vf500-colibri_vf50
+ - const: fsl,vf500
+
- description: VF610 based Boards
items:
- enum:
@@ -1725,6 +1731,12 @@ properties:
- const: toradex,vf610-colibri_vf61
- const: fsl,vf610
+ - description: Toradex Colibri VF61 Module on Iris Carrier Board
+ items:
+ - const: toradex,vf610-colibri_vf61-on-iris
+ - const: toradex,vf610-colibri_vf61
+ - const: fsl,vf610
+
- description: ZII's VF610 based Boards
items:
- enum:
--
2.54.0
next prev parent reply other threads:[~2026-08-10 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 14:00 [PATCH 0/3] ARM: dts: vf: Iris carrier board for the Colibri VF50 and VF61 Mehmet Fide
2026-08-10 14:00 ` [PATCH 1/3] ARM: dts: vf-colibri: apply the EXT_IO pin group Mehmet Fide
2026-08-10 14:00 ` [PATCH 2/3] ARM: dts: vf-colibri: name the SODIMM gpio lines Mehmet Fide
2026-08-10 14:00 ` [PATCH 3/3] ARM: dts: vf: add Iris carrier board support for Colibri VF50 and VF61 Mehmet Fide
2026-08-10 14:20 ` [PATCH v2 0/4] ARM: dts: vf: Iris carrier board for the " Mehmet Fide
2026-08-10 14:20 ` [PATCH v2 1/4] ARM: dts: vf-colibri: apply the EXT_IO pin group Mehmet Fide
2026-08-10 14:20 ` [PATCH v2 2/4] ARM: dts: vf-colibri: name the SODIMM gpio lines Mehmet Fide
2026-08-10 14:20 ` Mehmet Fide [this message]
2026-08-10 14:20 ` [PATCH v2 4/4] ARM: dts: vf: add Iris carrier board support for Colibri VF50 and VF61 Mehmet Fide
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=20260810142047.2811230-4-mehmet.fide@gmail.com \
--to=mehmet.fide@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco@dolcini.it \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--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 \
--cc=stefan@agner.ch \
/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