From: <Claudiu.Beznea@microchip.com>
To: <broonie@kernel.org>, <Ludovic.Desroches@microchip.com>,
<linus.walleij@linaro.org>, <Nicolas.Ferre@microchip.com>,
<alexandre.belloni@bootlin.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] pinctrl: at91: Remove pioc_index from struct at91_gpio_chip
Date: Fri, 17 Feb 2023 11:47:14 +0000 [thread overview]
Message-ID: <1df2c180-4ab6-b0c4-0e06-c56e3137ae40@microchip.com> (raw)
In-Reply-To: <20230216-gpio-at91-immutable-v1-2-44f52f148ab9@kernel.org>
On 16.02.2023 17:43, Mark Brown wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> The pioc_idx member of struct at91_gpio_chip is write only, just remove it.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>
> ---
> drivers/pinctrl/pinctrl-at91.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/pinctrl/pinctrl-at91.c b/drivers/pinctrl/pinctrl-at91.c
> index 8ecf52ec9b9b..a1db6ac9bd2e 100644
> --- a/drivers/pinctrl/pinctrl-at91.c
> +++ b/drivers/pinctrl/pinctrl-at91.c
> @@ -41,7 +41,6 @@ struct at91_pinctrl_mux_ops;
> * @next: bank sharing same clock
> * @pioc_hwirq: PIO bank interrupt identifier on AIC
> * @pioc_virq: PIO bank Linux virtual interrupt
> - * @pioc_idx: PIO bank index
> * @regbase: PIO bank virtual address
> * @clock: associated clock
> * @ops: at91 pinctrl mux ops
> @@ -55,7 +54,6 @@ struct at91_gpio_chip {
> struct at91_gpio_chip *next;
> int pioc_hwirq;
> int pioc_virq;
> - int pioc_idx;
> void __iomem *regbase;
> struct clk *clock;
> const struct at91_pinctrl_mux_ops *ops;
> @@ -1867,7 +1865,6 @@ static int at91_gpio_probe(struct platform_device *pdev)
> at91_chip->ops = (const struct at91_pinctrl_mux_ops *)
> of_match_device(at91_gpio_of_match, &pdev->dev)->data;
> at91_chip->pioc_virq = irq;
> - at91_chip->pioc_idx = alias_idx;
>
> at91_chip->clock = devm_clk_get(&pdev->dev, NULL);
> if (IS_ERR(at91_chip->clock)) {
>
> --
> 2.34.1
>
prev parent reply other threads:[~2023-02-17 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 15:43 [PATCH 0/2] pinctrl: at91: Minor cleanups Mark Brown
2023-02-16 15:43 ` [PATCH 1/2] pinctrl: at91: Make the irqchip immutable Mark Brown
2023-02-17 11:46 ` Claudiu.Beznea
2023-03-06 13:20 ` Linus Walleij
2023-03-06 13:42 ` Mark Brown
2023-03-07 3:31 ` Nicolas Ferre
2023-02-16 15:43 ` [PATCH 2/2] pinctrl: at91: Remove pioc_index from struct at91_gpio_chip Mark Brown
2023-02-17 11:47 ` Claudiu.Beznea [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=1df2c180-4ab6-b0c4-0e06-c56e3137ae40@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®