From: Neil Armstrong <neil.armstrong@linaro.org>
To: Jan Dakinevich <jan.dakinevich@salutedevices.com>,
Linus Walleij <linus.walleij@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] pinctrl/meson: fix typo in PDM's pin name
Date: Mon, 25 Mar 2024 14:59:10 +0100 [thread overview]
Message-ID: <82e09104-8006-4074-9700-2dec08194ac4@linaro.org> (raw)
In-Reply-To: <20240325113058.248022-1-jan.dakinevich@salutedevices.com>
On 25/03/2024 12:30, Jan Dakinevich wrote:
> Other pins have _a or _x suffix, but this one doesn't have any. Most
> likely this is a typo.
>
> Fixes: dabad1ff8561 ("pinctrl: meson: add pinctrl driver support for Meson-A1 SoC")
> Signed-off-by: Jan Dakinevich <jan.dakinevich@salutedevices.com>
> ---
> Links:
>
> [1] https://lore.kernel.org/lkml/20240314232201.2102178-1-jan.dakinevich@salutedevices.com/
>
> Changes:
> v1 -> v2: Detached from v1's series (patch 15)
>
> drivers/pinctrl/meson/pinctrl-meson-a1.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/pinctrl/meson/pinctrl-meson-a1.c b/drivers/pinctrl/meson/pinctrl-meson-a1.c
> index 79f5d753d7e1..50a87d9618a8 100644
> --- a/drivers/pinctrl/meson/pinctrl-meson-a1.c
> +++ b/drivers/pinctrl/meson/pinctrl-meson-a1.c
> @@ -250,7 +250,7 @@ static const unsigned int pdm_dclk_x_pins[] = { GPIOX_10 };
> static const unsigned int pdm_din2_a_pins[] = { GPIOA_6 };
> static const unsigned int pdm_din1_a_pins[] = { GPIOA_7 };
> static const unsigned int pdm_din0_a_pins[] = { GPIOA_8 };
> -static const unsigned int pdm_dclk_pins[] = { GPIOA_9 };
> +static const unsigned int pdm_dclk_a_pins[] = { GPIOA_9 };
>
> /* gen_clk */
> static const unsigned int gen_clk_x_pins[] = { GPIOX_7 };
> @@ -591,7 +591,7 @@ static struct meson_pmx_group meson_a1_periphs_groups[] = {
> GROUP(pdm_din2_a, 3),
> GROUP(pdm_din1_a, 3),
> GROUP(pdm_din0_a, 3),
> - GROUP(pdm_dclk, 3),
> + GROUP(pdm_dclk_a, 3),
> GROUP(pwm_c_a, 3),
> GROUP(pwm_b_a, 3),
>
> @@ -755,7 +755,7 @@ static const char * const spi_a_groups[] = {
>
> static const char * const pdm_groups[] = {
> "pdm_din0_x", "pdm_din1_x", "pdm_din2_x", "pdm_dclk_x", "pdm_din2_a",
> - "pdm_din1_a", "pdm_din0_a", "pdm_dclk",
> + "pdm_din1_a", "pdm_din0_a", "pdm_dclk_a",
> };
>
> static const char * const gen_clk_groups[] = {
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-25 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 11:30 [PATCH v2] pinctrl/meson: fix typo in PDM's pin name Jan Dakinevich
2024-03-25 13:59 ` Neil Armstrong [this message]
2024-03-28 9:43 ` 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=82e09104-8006-4074-9700-2dec08194ac4@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=jan.dakinevich@salutedevices.com \
--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 \
/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