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>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] ARM: dts: vf: Iris carrier board for the Colibri VF50 and VF61
Date: Mon, 10 Aug 2026 16:00:50 +0200 [thread overview]
Message-ID: <20260810140053.2793495-1-mehmet.fide@gmail.com> (raw)
From: Mehmet Fide <mehmet.fide@screeningeagle.com>
Mainline carries Iris carrier board 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. This series adds the
carrier, and picks up two things on the module tree on the way.
Patch 1 applies the EXT_IO pin group, which is defined in the module dtsi
and referenced by nothing. It replaces a patch I sent on 2026-08-07 that
hogged the group on &iomuxc; hanging it off gpio2 instead avoids the
fw_devlink dependency cycle that a pin controller referencing its own
child produces.
Patch 2 names the SODIMM lines, as the i.MX Colibri trees already do.
Patch 3 adds the carrier itself.
All three are tested on a Colibri VF50 on an Iris V1.1 running 6.18.44.
Mehmet Fide (3):
ARM: dts: vf-colibri: apply the EXT_IO pin group
ARM: dts: vf-colibri: name the SODIMM gpio lines
ARM: dts: vf: add Iris carrier board support for Colibri VF50 and VF61
arch/arm/boot/dts/nxp/vf/Makefile | 2 +
arch/arm/boot/dts/nxp/vf/vf-colibri-iris.dtsi | 125 ++++++++++++++
arch/arm/boot/dts/nxp/vf/vf-colibri.dtsi | 153 ++++++++++++++++++
.../boot/dts/nxp/vf/vf500-colibri-iris.dts | 14 ++
.../boot/dts/nxp/vf/vf610-colibri-iris.dts | 13 ++
5 files changed, 307 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
--
2.54.0
next reply other threads:[~2026-08-10 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 14:00 Mehmet Fide [this message]
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 ` [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=20260810140053.2793495-1-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=marcel.ziswiler@toradex.com \
--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