From: Neil Armstrong <neil.armstrong@linaro.org>
To: "Martin Hundebøll" <martin@geanix.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Kevin Hilman" <khilman@baylibre.com>,
"Jerome Brunet" <jbrunet@baylibre.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Xingyu Chen" <xingyu.chen@amlogic.com>,
"Yixun Lan" <yixun.lan@amlogic.com>
Cc: stable@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] pinctrl: meson-axg: add missing GPIOA_18 gpio group
Date: Fri, 12 May 2023 12:11:30 +0200 [thread overview]
Message-ID: <e2bd6ca0-ffa1-a1f3-340b-6522dacd099d@linaro.org> (raw)
In-Reply-To: <20230512064925.133516-1-martin@geanix.com>
On 12/05/2023 08:49, Martin Hundebøll wrote:
> Without this, the gpio cannot be explicitly mux'ed to its gpio function.
>
> Fixes: 83c566806a68a ("pinctrl: meson-axg: Add new pinctrl driver for Meson AXG SoC")
> Cc: stable@vger.kernel.org
> Signed-off-by: Martin Hundebøll <martin@geanix.com>
> ---
> Changes since first mail:
> * Added Cc: stable to commit message
> * Expanded To: and Cc: with full list from get_maintainers.pl
>
> drivers/pinctrl/meson/pinctrl-meson-axg.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/pinctrl/meson/pinctrl-meson-axg.c b/drivers/pinctrl/meson/pinctrl-meson-axg.c
> index 7bfecdfba177..d249a035c2b9 100644
> --- a/drivers/pinctrl/meson/pinctrl-meson-axg.c
> +++ b/drivers/pinctrl/meson/pinctrl-meson-axg.c
> @@ -400,6 +400,7 @@ static struct meson_pmx_group meson_axg_periphs_groups[] = {
> GPIO_GROUP(GPIOA_15),
> GPIO_GROUP(GPIOA_16),
> GPIO_GROUP(GPIOA_17),
> + GPIO_GROUP(GPIOA_18),
> GPIO_GROUP(GPIOA_19),
> GPIO_GROUP(GPIOA_20),
>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
next prev parent reply other threads:[~2023-05-12 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 6:49 [PATCH RESEND] pinctrl: meson-axg: add missing GPIOA_18 gpio group Martin Hundebøll
2023-05-12 9:24 ` Dmitry Rokosov
2023-05-12 10:11 ` Neil Armstrong [this message]
2023-05-16 13:01 ` Linus Walleij
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=e2bd6ca0-ffa1-a1f3-340b-6522dacd099d@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=martin@geanix.com \
--cc=stable@vger.kernel.org \
--cc=xingyu.chen@amlogic.com \
--cc=yixun.lan@amlogic.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).