From: Patrick DELAUNAY <patrick.delaunay@foss.st.com>
To: Patrice Chotard <patrice.chotard@foss.st.com>, <u-boot@lists.denx.de>
Cc: U-Boot STM32 <uboot-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH v3 3/4] pinctrl: pinctrl_stm32: Populate uc_priv->name[] with pinmux node's name
Date: Tue, 30 Aug 2022 14:21:35 +0200 [thread overview]
Message-ID: <462adc83-d755-e2a7-8724-1dcf2a867339@foss.st.com> (raw)
In-Reply-To: <20220830120914.2329522-4-patrice.chotard@foss.st.com>
Hi,
On 8/30/22 14:09, Patrice Chotard wrote:
> Populate uc_priv->name[] with pinmux node's name in order to indicate
> the pinmuxing's name in case GPIO is configured in alternate.
>
> For example, for STM32 SoC's based platform, "gpio status" command
> output :
>
> before
> Bank GPIOZ:
> GPIOZ0: unused : 0 [ ]
> GPIOZ1: unused : 0 [ ]
> GPIOZ2: unused : 0 [ ]
> GPIOZ3: unused : 0 [ ]
> GPIOZ4: func
> GPIOZ5: func
> GPIOZ6: unused : 0 [ ]
> GPIOZ7: unused : 0 [ ]
> GPIOZ8: unknown
> GPIOZ9: unknown
> GPIOZ10: unknown
> GPIOZ11: unknown
> GPIOZ12: unknown
> GPIOZ13: unknown
> GPIOZ14: unknown
> GPIOZ15: unknown
>
> After
> Bank GPIOZ:
> GPIOZ0: unused : 0 [ ]
> GPIOZ1: unused : 0 [ ]
> GPIOZ2: unused : 0 [ ]
> GPIOZ3: unused : 0 [ ]
> GPIOZ4: func i2c4-0
> GPIOZ5: func i2c4-0
> GPIOZ6: unused : 0 [ ]
> GPIOZ7: unused : 0 [ ]
> GPIOZ8: unknown
> GPIOZ9: unknown
> GPIOZ10: unknown
> GPIOZ11: unknown
> GPIOZ12: unknown
> GPIOZ13: unknown
> GPIOZ14: unknown
> GPIOZ15: unknown
>
> Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
> ---
>
> (no changes since v1)
>
> drivers/pinctrl/pinctrl_stm32.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
Reviewed-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
Thanks
Patrick
next prev parent reply other threads:[~2022-08-30 12:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 12:09 [PATCH v3 0/4] gpio: update gpio_get_status() Patrice Chotard
2022-08-30 12:09 ` [PATCH v3 1/4] gpio: Allow to print pin's label even for pin with GPIOF_FUNC function Patrice Chotard
2022-08-30 12:16 ` Patrick DELAUNAY
2022-09-15 14:02 ` Tom Rini
2022-08-30 12:09 ` [PATCH v3 2/4] gpio: Fix pin's status display for pin with GPIOF_UNUSED function Patrice Chotard
2022-08-30 12:16 ` Patrick DELAUNAY
2022-09-15 14:03 ` Tom Rini
2022-08-30 12:09 ` [PATCH v3 3/4] pinctrl: pinctrl_stm32: Populate uc_priv->name[] with pinmux node's name Patrice Chotard
2022-08-30 12:21 ` Patrick DELAUNAY [this message]
2022-09-15 14:03 ` Tom Rini
2022-08-30 12:09 ` [PATCH v3 4/4] gpio: sandbox: Add GPIOD_IS_AF for gpio configured in alternate function Patrice Chotard
2022-08-30 12:24 ` Patrick DELAUNAY
2022-09-15 14:03 ` Tom Rini
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=462adc83-d755-e2a7-8724-1dcf2a867339@foss.st.com \
--to=patrick.delaunay@foss.st.com \
--cc=patrice.chotard@foss.st.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-stm32@st-md-mailman.stormreply.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).