[PATCH v2 4/4] ARM: dts: vf: add Iris carrier board support for Colibri VF50 and VF61
Krzysztof Kozlowski
krzk at kernel.org
Thu Aug 13 01:22:04 PDT 2026
On Mon, Aug 10, 2026 at 04:20:47PM +0200, Mehmet Fide wrote:
> 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
Odd license ("or later"), but I guess this is a derived work of existing
code.
> +/*
> + * 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>;
> + };
This regulator is not really used. Drop, because there is no need to
represent chain of uncontrollable regulators whose purpose is only input
to other regulator.
> +
> + 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>;
> + };
> +};
Best regards,
Krzysztof
More information about the linux-arm-kernel
mailing list