From: Daniel Baluta <daniel.baluta@oss.nxp.com>
To: Ian Ray <ian.ray@gehealthcare.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] ARM: dts: imx: b850v3: Define GPIO line names
Date: Tue, 17 Feb 2026 15:23:02 +0200 [thread overview]
Message-ID: <600ec825-4402-46a5-85df-1e57f0ade49d@oss.nxp.com> (raw)
In-Reply-To: <20260217125952.53997-4-ian.ray@gehealthcare.com>
On 2/17/26 14:59, Ian Ray wrote:
> @@ -72,6 +72,18 @@ lvds0_out: endpoint {
> };
> };
>
> +&gpio4 {
> + gpio-line-names =
> + "", "", "", "",
> + "", "", "", "",
> + "", "", "", "",
> + "", "", "PWGIN", "",
> + "", "", "", "",
> + "", "", "", "",
> + "", "", "", "",
> + "", "", "", "";
> +};
Looking at my latest version of code this node should be a little bit up in the
file to preserve the alphabetical sorting of references modification.
e.g
+&gpio4 {
... then
comes
&ldb {
etc.
next prev parent reply other threads:[~2026-02-17 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 12:59 [PATCH 0/4] ARM: dts: imx: {bx50v3,b850v3}: Update device trees Ian Ray
2026-02-17 12:59 ` [PATCH 1/4] ARM: dts: imx: bx50v3: Configure switch PHY max-speed Ian Ray
2026-02-17 14:53 ` Andrew Lunn
2026-02-17 15:07 ` Ian Ray
2026-02-17 12:59 ` [PATCH 2/4] ARM: dts: imx: bx50v3: Configure phy-mode Ian Ray
2026-02-17 13:08 ` Daniel Baluta
2026-02-17 13:15 ` Ian Ray
2026-02-17 14:58 ` Andrew Lunn
2026-02-17 15:15 ` Ian Ray
2026-02-17 12:59 ` [PATCH 3/4] ARM: dts: imx: b850v3: Define GPIO line names Ian Ray
2026-02-17 13:23 ` Daniel Baluta [this message]
2026-02-17 13:21 ` Ian Ray
2026-02-17 12:59 ` [PATCH 4/4] ARM: dts: imx: b850v3: Disable usdhc4 Ian Ray
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=600ec825-4402-46a5-85df-1e57f0ade49d@oss.nxp.com \
--to=daniel.baluta@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=ian.ray@gehealthcare.com \
--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=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
/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