From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Marek Vasut <marex@denx.de>, <linux-arm-kernel@lists.infradead.org>
Cc: Patrice Chotard <patrice.chotard@foss.st.com>,
Patrick Delaunay <patrick.delaunay@foss.st.com>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH V3 4/4] ARM: dts: stm32: Update GPIO line names on PicoITX
Date: Thu, 1 Apr 2021 10:35:29 +0200 [thread overview]
Message-ID: <2a0d3d62-06a2-53da-e84f-10f0578ef3cb@foss.st.com> (raw)
In-Reply-To: <20210329193614.13374-4-marex@denx.de>
Hi Marek
On 3/29/21 9:36 PM, Marek Vasut wrote:
> Use more specific custom GPIO line names which denote exactly where
> the GPIO came from, i.e. the base board. Also, update the new blank
> GPIO line names set up by stm32mp15xx-dhcom-som.dtsi back to their
> original values.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
> Cc: Patrice Chotard <patrice.chotard@foss.st.com>
> Cc: Patrick Delaunay <patrick.delaunay@foss.st.com>
> Cc: linux-stm32@st-md-mailman.stormreply.com
> To: linux-arm-kernel@lists.infradead.org
Series applied on stm32-next.
Regards
Alex
> ---
> V2: New patch
> V3: No change
> ---
> arch/arm/boot/dts/stm32mp15xx-dhcom-picoitx.dtsi | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm/boot/dts/stm32mp15xx-dhcom-picoitx.dtsi b/arch/arm/boot/dts/stm32mp15xx-dhcom-picoitx.dtsi
> index cd3a1798ca68..ba816ef8b9b2 100644
> --- a/arch/arm/boot/dts/stm32mp15xx-dhcom-picoitx.dtsi
> +++ b/arch/arm/boot/dts/stm32mp15xx-dhcom-picoitx.dtsi
> @@ -57,22 +57,22 @@ usb-port-power-hog {
>
> &gpioc {
> gpio-line-names = "", "", "", "",
> - "", "", "In1", "",
> + "", "", "PicoITX-In1", "",
> "", "", "", "",
> "", "", "", "";
> };
>
> &gpiod {
> gpio-line-names = "", "", "", "",
> - "", "", "", "",
> - "", "", "", "Out1",
> - "Out2", "", "", "";
> + "", "", "DHCOM-B", "",
> + "", "", "", "PicoITX-Out1",
> + "PicoITX-Out2", "", "", "";
> };
>
> &gpiog {
> - gpio-line-names = "In2", "", "", "",
> - "", "", "", "",
> + gpio-line-names = "PicoITX-In2", "", "", "",
> "", "", "", "",
> + "DHCOM-L", "", "", "",
> "", "", "", "";
> };
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-04-01 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 19:36 [PATCH V3 1/4] ARM: dts: stm32: Fill GPIO line names on DHCOM SoM Marek Vasut
2021-03-29 19:36 ` [PATCH V3 2/4] ARM: dts: stm32: Fill GPIO line names on AV96 Marek Vasut
2021-03-29 19:36 ` [PATCH V3 3/4] ARM: dts: stm32: Update GPIO line names on DRC02 Marek Vasut
2021-03-29 19:36 ` [PATCH V3 4/4] ARM: dts: stm32: Update GPIO line names on PicoITX Marek Vasut
2021-04-01 8:35 ` Alexandre TORGUE [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=2a0d3d62-06a2-53da-e84f-10f0578ef3cb@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marex@denx.de \
--cc=patrice.chotard@foss.st.com \
--cc=patrick.delaunay@foss.st.com \
/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;
as well as URLs for NNTP newsgroup(s).