From: Frank Li <Frank.li@oss.nxp.com>
To: Mehmet Fide <mehmet.fide@gmail.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Frank Li <Frank.Li@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Stefan Agner <stefan@agner.ch>,
Fabio Estevam <festevam@gmail.com>, 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, imx@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Mehmet Fide <mehmet.fide@screeningeagle.com>
Subject: Re: [PATCH v3 2/4] ARM: dts: vf-colibri: name the SODIMM gpio lines
Date: Thu, 13 Aug 2026 10:20:48 -0500 [thread overview]
Message-ID: <an3g0CsaF9aUp4nh@SMW015318> (raw)
In-Reply-To: <20260813140600.1824949-3-mehmet.fide@gmail.com>
On Thu, Aug 13, 2026 at 04:05:58PM +0200, Mehmet Fide wrote:
> From: Mehmet Fide <mehmet.fide@screeningeagle.com>
>
> The Colibri modules expose most of their GPIOs on numbered SODIMM pins,
> and the i.MX ones already carry those numbers as gpio-line-names, so the
> gpiod tools print SODIMM_43 rather than a bank and an offset. Do the same
> for the Vybrid modules.
>
> The 99 names come from the pinout table of the Colibri VFxx datasheet
> (Toradex 101355). Verified on a Colibri VF50, where gpioinfo now names
> every pin the datasheet lists.
>
> Signed-off-by: Mehmet Fide <mehmet.fide@screeningeagle.com>
> ---
> arch/arm/boot/dts/nxp/vf/vf-colibri.dtsi | 144 +++++++++++++++++++++++
> 1 file changed, 144 insertions(+)
>
> diff --git a/arch/arm/boot/dts/nxp/vf/vf-colibri.dtsi b/arch/arm/boot/dts/nxp/vf/vf-colibri.dtsi
> index 74afc7b0d74b..04b5d532b2c5 100644
> --- a/arch/arm/boot/dts/nxp/vf/vf-colibri.dtsi
> +++ b/arch/arm/boot/dts/nxp/vf/vf-colibri.dtsi
> @@ -170,6 +170,120 @@ &usbphy1 {
> status = "okay";
> };
>
> +&gpio0 {
> + gpio-line-names = "",
> + "",
> + "SODIMM_89",
> + "",
> + "",
Can you move 4 pins to one line to file compact?
Frank
> + "SODIMM_102",
> + "SODIMM_18",
> + "SODIMM_134",
> + "SODIMM_16",
> + "SODIMM_14",
> + "SODIMM_23",
> + "",
> + "",
> + "",
> + "SODIMM_47",
> + "SODIMM_190",
> + "SODIMM_192",
> + "SODIMM_49",
> + "SODIMM_51",
> + "SODIMM_53",
> + "SODIMM_37",
> + "SODIMM_29",
> + "",
> + "SODIMM_30",
> + "SODIMM_20",
> + "SODIMM_24",
> + "SODIMM_21",
> + "SODIMM_19",
> + "SODIMM_94",
> + "SODIMM_81",
> + "SODIMM_28";
> +};
> +
> +&gpio1 {
> + gpio-line-names = "SODIMM_35",
> + "SODIMM_33",
> + "SODIMM_27",
> + "SODIMM_25",
> + "SODIMM_196",
> + "SODIMM_194",
> + "SODIMM_63",
> + "SODIMM_55",
> + "SODIMM_65",
> + "SODIMM_45",
> + "SODIMM_43",
> + "SODIMM_73",
> + "SODIMM_77",
> + "SODIMM_71",
> + "SODIMM_98",
> + "SODIMM_101",
> + "SODIMM_103",
> + "SODIMM_79",
> + "SODIMM_97",
> + "",
> + "",
> + "SODIMM_85",
> + "",
> + "",
> + "",
> + "",
> + "",
> + "",
> + "",
> + "",
> + "",
> + "SODIMM_106";
> +};
> +
> +&gpio3 {
> + gpio-line-names = "SODIMM_105",
> + "",
> + "SODIMM_93",
> + "",
> + "",
> + "",
> + "",
> + "SODIMM_95",
> + "SODIMM_22",
> + "SODIMM_68",
> + "SODIMM_82",
> + "SODIMM_56",
> + "SODIMM_131",
> + "SODIMM_44",
> + "SODIMM_144",
> + "SODIMM_146",
> + "SODIMM_52",
> + "SODIMM_54",
> + "SODIMM_66",
> + "SODIMM_64",
> + "SODIMM_57",
> + "SODIMM_61",
> + "SODIMM_140",
> + "SODIMM_142",
> + "SODIMM_80",
> + "SODIMM_46",
> + "SODIMM_62",
> + "SODIMM_48",
> + "SODIMM_74",
> + "SODIMM_50",
> + "SODIMM_136",
> + "SODIMM_138";
> +};
> +
> +&gpio4 {
> + gpio-line-names = "SODIMM_76",
> + "SODIMM_70",
> + "SODIMM_60",
> + "SODIMM_58",
> + "SODIMM_78",
> + "SODIMM_72",
> + "SODIMM_96";
> +};
> +
> &gpio2 {
> /*
> * EXT_IO_0..2 belong to no device, so hog the pin group here rather
> @@ -177,6 +291,36 @@ &gpio2 {
> */
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_gpio_ext>;
> +
> + gpio-line-names = "SODIMM_69",
> + "SODIMM_99",
> + "SODIMM_104",
> + "SODIMM_107",
> + "SODIMM_127",
> + "SODIMM_184",
> + "SODIMM_186",
> + "",
> + "",
> + "",
> + "",
> + "",
> + "",
> + "",
> + "",
> + "SODIMM_38",
> + "SODIMM_36",
> + "SODIMM_34",
> + "SODIMM_32",
> + "SODIMM_129",
> + "SODIMM_86",
> + "SODIMM_90",
> + "SODIMM_92",
> + "SODIMM_88",
> + "SODIMM_133",
> + "SODIMM_135",
> + "SODIMM_188",
> + "SODIMM_75",
> + "SODIMM_100";
> };
>
> &iomuxc {
> --
> 2.54.0
>
>
next prev parent reply other threads:[~2026-08-13 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 14:05 [PATCH v3 0/4] ARM: dts: vf: Iris carrier board for the Colibri VF50 and VF61 Mehmet Fide
2026-08-13 14:05 ` [PATCH v3 1/4] ARM: dts: vf-colibri: apply the EXT_IO pin group Mehmet Fide
2026-08-13 14:05 ` [PATCH v3 2/4] ARM: dts: vf-colibri: name the SODIMM gpio lines Mehmet Fide
2026-08-13 15:20 ` Frank Li [this message]
2026-08-13 14:05 ` [PATCH v3 3/4] dt-bindings: arm: fsl: add the Colibri VF50 and VF61 on Iris Mehmet Fide
2026-08-13 14:13 ` sashiko-bot
2026-08-13 14:06 ` [PATCH v3 4/4] ARM: dts: vf: add Iris carrier board support for Colibri VF50 and VF61 Mehmet Fide
2026-08-13 14:16 ` sashiko-bot
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=an3g0CsaF9aUp4nh@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco@dolcini.it \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mehmet.fide@gmail.com \
--cc=mehmet.fide@screeningeagle.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