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 4/4] ARM: dts: vf: add Iris carrier board support for Colibri VF50 and VF61
Date: Mon, 10 Aug 2026 16:20:47 +0200 [thread overview]
Message-ID: <20260810142047.2811230-5-mehmet.fide@gmail.com> (raw)
In-Reply-To: <20260810142047.2811230-1-mehmet.fide@gmail.com>
From: Mehmet Fide <mehmet.fide@screeningeagle.com>
Mainline carries Iris device trees for every i.MX Colibri but none for the
Vybrid ones, so a VF50 or VF61 on that carrier has nothing to boot with
except the eval board tree, which describes different hardware.
Add the carrier, following the layout of the i.MX Iris trees: a common
dtsi and one dts per module. It enables the microSD slot, the three UARTs,
SPI, Ethernet, USB and the M41T0 clock on the carrier, switches USB host
VBUS through a regulator on SODIMM 129, and hogs the two GPIOs that turn
the RS232 transceivers on, SODIMM 102 and 104. The touchscreen is an
add-on rather than part of the board, so it is left out.
This describes an Iris V1.1. A V2.0 carries the same signals on the same
pins; what it adds, and what this does not describe, is the regulator on
SODIMM 100 that can cut power to the uSD slot.
Tested on a Colibri VF50 on an Iris V1.1 running 6.18: Ethernet at
100Mbps/Full, a USB dongle enumerating once the VBUS regulator is in
place, the RTC read back over i2c0, all three UARTs, the SPI controller
registering, the microSD slot, and both hogs holding their pins.
Signed-off-by: Mehmet Fide <mehmet.fide@screeningeagle.com>
---
arch/arm/boot/dts/nxp/vf/Makefile | 2 +
arch/arm/boot/dts/nxp/vf/vf-colibri-iris.dtsi | 125 ++++++++++++++++++
.../boot/dts/nxp/vf/vf500-colibri-iris.dts | 14 ++
.../boot/dts/nxp/vf/vf610-colibri-iris.dts | 13 ++
4 files changed, 154 insertions(+)
create mode 100644 arch/arm/boot/dts/nxp/vf/vf-colibri-iris.dtsi
create mode 100644 arch/arm/boot/dts/nxp/vf/vf500-colibri-iris.dts
create mode 100644 arch/arm/boot/dts/nxp/vf/vf610-colibri-iris.dts
diff --git a/arch/arm/boot/dts/nxp/vf/Makefile b/arch/arm/boot/dts/nxp/vf/Makefile
index 0a4a7f9..47be8bc 100644
--- a/arch/arm/boot/dts/nxp/vf/Makefile
+++ b/arch/arm/boot/dts/nxp/vf/Makefile
@@ -1,8 +1,10 @@
# SPDX-License-Identifier: GPL-2.0
dtb-$(CONFIG_SOC_VF610) += \
vf500-colibri-eval-v3.dtb \
+ vf500-colibri-iris.dtb \
vf610-bk4.dtb \
vf610-colibri-eval-v3.dtb \
+ vf610-colibri-iris.dtb \
vf610m4-colibri.dtb \
vf610-cosmic.dtb \
vf610m4-cosmic.dtb \
diff --git a/arch/arm/boot/dts/nxp/vf/vf-colibri-iris.dtsi b/arch/arm/boot/dts/nxp/vf/vf-colibri-iris.dtsi
new file mode 100644
index 0000000..d0fa107
--- /dev/null
+++ b/arch/arm/boot/dts/nxp/vf/vf-colibri-iris.dtsi
@@ -0,0 +1,125 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+/*
+ * Copyright 2026 Mehmet Fide
+ *
+ * Toradex Iris carrier board V1.1, common part for Colibri VF50 and VF61.
+ *
+ * The Colibri modules are pin compatible, so the carrier signals sit on the
+ * same SODIMM pins as they do for the i.MX modules, whose Iris device trees
+ * are already upstream. The two SODIMM pins below are taken from the Colibri
+ * VFxx datasheet (102 -> PTA12 -> PORT0[5], 104 -> PTD28 -> PORT2[2]).
+ *
+ * An Iris V2.0 carries the same signals on the same pins, so everything here
+ * works on it as well. What it adds is a regulator on SODIMM 100 that can cut
+ * power to the uSD slot, which this file does not describe.
+ */
+
+/ {
+ chosen {
+ stdout-path = "serial0:115200n8";
+ };
+
+ reg_5v0: regulator-5v0 {
+ compatible = "regulator-fixed";
+ regulator-name = "5V";
+ regulator-min-microvolt = <5000000>;
+ regulator-max-microvolt = <5000000>;
+ };
+
+ reg_usbh_vbus: regulator-usbh-vbus {
+ compatible = "regulator-fixed";
+ pinctrl-names = "default";
+ pinctrl-0 = <&pinctrl_usbh1_reg>;
+ regulator-name = "VCC_USB[1-4]";
+ regulator-min-microvolt = <5000000>;
+ regulator-max-microvolt = <5000000>;
+ gpio = <&gpio2 19 GPIO_ACTIVE_LOW>; /* SODIMM 129, USBH_PEN */
+ vin-supply = <®_5v0>;
+ };
+};
+
+&gpio0 {
+ /*
+ * The RS232 transceivers on the carrier are switched on by these two
+ * lines. Delete the hog to turn a transceiver off from userspace.
+ * The pin group belongs to the gpio controller rather than to iomuxc,
+ * which would depend on its own child and log a dependency cycle.
+ */
+ pinctrl-names = "default";
+ pinctrl-0 = <&pinctrl_iris_uart1_tx_on>;
+
+ uart1-tx-on-hog {
+ gpio-hog;
+ gpios = <5 GPIO_ACTIVE_HIGH>; /* SODIMM 102 */
+ output-high;
+ };
+};
+
+&gpio2 {
+ pinctrl-names = "default";
+ pinctrl-0 = <&pinctrl_iris_uart25_tx_on>;
+
+ uart25-tx-on-hog {
+ gpio-hog;
+ gpios = <2 GPIO_ACTIVE_HIGH>; /* SODIMM 104 */
+ output-high;
+ };
+};
+
+&iomuxc {
+ pinctrl_iris_uart1_tx_on: irisuart1txongrp {
+ fsl,pins = <
+ VF610_PAD_PTA12__GPIO_5 0x22ef
+ >;
+ };
+
+ pinctrl_iris_uart25_tx_on: irisuart25txongrp {
+ fsl,pins = <
+ VF610_PAD_PTD28__GPIO_66 0x22ef
+ >;
+ };
+};
+
+/* Colibri SSP, on the extension connector */
+&dspi1 {
+ status = "okay";
+};
+
+&esdhc1 {
+ status = "okay";
+};
+
+&fec1 {
+ status = "okay";
+};
+
+&i2c0 {
+ status = "okay";
+
+ /* M41T0M6 real time clock on the carrier */
+ rtc@68 {
+ compatible = "st,m41t0";
+ reg = <0x68>;
+ };
+};
+
+&uart0 {
+ status = "okay";
+};
+
+&uart1 {
+ status = "okay";
+};
+
+&uart2 {
+ status = "okay";
+};
+
+&usbdev0 {
+ status = "okay";
+};
+
+&usbh1 {
+ vbus-supply = <®_usbh_vbus>;
+ status = "okay";
+};
diff --git a/arch/arm/boot/dts/nxp/vf/vf500-colibri-iris.dts b/arch/arm/boot/dts/nxp/vf/vf500-colibri-iris.dts
new file mode 100644
index 0000000..53dd252
--- /dev/null
+++ b/arch/arm/boot/dts/nxp/vf/vf500-colibri-iris.dts
@@ -0,0 +1,14 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+/*
+ * Copyright 2026 Mehmet Fide
+ */
+
+/dts-v1/;
+#include "vf500-colibri.dtsi"
+#include "vf-colibri-iris.dtsi"
+
+/ {
+ model = "Toradex Colibri VF50 on Iris Carrier Board";
+ compatible = "toradex,vf500-colibri_vf50-on-iris", "toradex,vf500-colibri_vf50", "fsl,vf500";
+};
+
diff --git a/arch/arm/boot/dts/nxp/vf/vf610-colibri-iris.dts b/arch/arm/boot/dts/nxp/vf/vf610-colibri-iris.dts
new file mode 100644
index 0000000..2882c87
--- /dev/null
+++ b/arch/arm/boot/dts/nxp/vf/vf610-colibri-iris.dts
@@ -0,0 +1,13 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+/*
+ * Copyright 2026 Mehmet Fide
+ */
+
+/dts-v1/;
+#include "vf610-colibri.dtsi"
+#include "vf-colibri-iris.dtsi"
+
+/ {
+ model = "Toradex Colibri VF61 on Iris Carrier Board";
+ compatible = "toradex,vf610-colibri_vf61-on-iris", "toradex,vf610-colibri_vf61", "fsl,vf610";
+};
--
2.54.0
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 ` [PATCH v2 3/4] dt-bindings: arm: fsl: add the Colibri VF50 and VF61 on Iris Mehmet Fide
2026-08-10 14:20 ` Mehmet Fide [this message]
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-5-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