From: Mark Brown <broonie@kernel.org>
To: Ludovic Desroches <ludovic.desroches@microchip.com>,
Linus Walleij <linus.walleij@linaro.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [PATCH 0/2] pinctrl: at91: Minor cleanups
Date: Thu, 16 Feb 2023 15:43:56 +0000 [thread overview]
Message-ID: <20230216-gpio-at91-immutable-v1-0-44f52f148ab9@kernel.org> (raw)
A few cleanups for the at91 driver, making the GPIO irqchip
immutable and removing an unused member from the driver data.
The driver is still using statically assigned GPIO numbers, we
can't just remove that since the driver itself is still relying
on them even if there are no longer board files for this
platform.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (2):
pinctrl: at91: Make the irqchip immutable
pinctrl: at91: Remove pioc_index from struct at91_gpio_chip
drivers/pinctrl/pinctrl-at91.c | 28 ++++++++++++++++++++++++----
1 file changed, 24 insertions(+), 4 deletions(-)
---
base-commit: 1b929c02afd37871d5afb9d498426f83432e71c2
change-id: 20230216-gpio-at91-immutable-53fcb995b285
Best regards,
--
Mark Brown <broonie@kernel.org>
next reply other threads:[~2023-02-16 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 15:43 Mark Brown [this message]
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
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=20230216-gpio-at91-immutable-v1-0-44f52f148ab9@kernel.org \
--to=broonie@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.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).