From: Frank.Li@oss.nxp.com
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Francesco Dolcini <francesco@dolcini.it>
Cc: Frank Li <Frank.Li@nxp.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v1] arm64: dts: freescale: imx8mp-toradex-smarc: fix SMARC_SLEEP# gpio-line-names typo
Date: Wed, 23 Sep 2026 15:58:46 -0400 [thread overview]
Message-ID: <179019352263.3733294.14111787723423970974.b4-ty@b4> (raw)
In-Reply-To: <20260915201411.23118-1-francesco@dolcini.it>
From: Frank Li <Frank.Li@nxp.com>
On Tue, 15 Sep 2026 22:14:10 +0200, Francesco Dolcini wrote:
> gpio3's gpio-line-names has "SLEEP#" instead of "SMARC_SLEEP#" for the
> SMARC SLEEP# connector signal, while the gpio-keys node driven by the
> very same GPIO line already labels it "SMARC_SLEEP#", and the imx95
> Toradex SMARC variant names the equivalent line "SMARC_SLEEP#" too.
>
> GPIO line names are meant to be stable across the whole Toradex SMARC
> family, using the official SMARC-connector signal names from the
> SMARC specification and the SoM datasheet's pin assignment table, so
> userspace GPIO tooling that looks up a line by name works the same on
> any Toradex SMARC board.
>
> [...]
Applied, thanks!
[1/1] arm64: dts: freescale: imx8mp-toradex-smarc: fix SMARC_SLEEP# gpio-line-names typo
commit: 90bc5a53c7f0733ec37a5c041b4e1aefa3d8d965
Best regards,
--
Frank Li <Frank.Li@nxp.com>
prev parent reply other threads:[~2026-09-23 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 20:14 [PATCH v1] arm64: dts: freescale: imx8mp-toradex-smarc: fix SMARC_SLEEP# gpio-line-names typo Francesco Dolcini
2026-09-23 19:58 ` Frank.Li [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=179019352263.3733294.14111787723423970974.b4-ty@b4 \
--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@toradex.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=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=stable@vger.kernel.org \
/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