From: <nicolas.ferre@microchip.com>
To: <linux-gpio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: <linux-kernel@vger.kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Ryan Wanner <Ryan.Wanner@microchip.com>
Subject: [PATCH] pinctrl: at91-pio4: Add sama7d65 pio4 support
Date: Mon, 5 Jan 2026 10:59:56 +0100 [thread overview]
Message-ID: <20260105095956.19615-1-nicolas.ferre@microchip.com> (raw)
From: Ryan Wanner <Ryan.Wanner@microchip.com>
Add sama7d65 compatibility string.
Sama7d65 does not have a full last bank of PIO lines similar to the
Sama7g54 SoC. Sama7d65 only has 14 lines on the last PIO bank not the
full 32; adjusting the SoC attributes accordingly.
Signed-off-by: Ryan Wanner <Ryan.Wanner@microchip.com>
Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
---
Hi,
dt-bindings already up-to-date with this new compatible string by:
https://lore.kernel.org/821255840c09d8d9cebbb1f2daaedd8a7c138875.1736522006.git.Ryan.Wanner@microchip.com
(even if still .txt)
Regards,
Nicolas
drivers/pinctrl/pinctrl-at91-pio4.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/drivers/pinctrl/pinctrl-at91-pio4.c b/drivers/pinctrl/pinctrl-at91-pio4.c
index ec5351fc282e..41cbb46ac589 100644
--- a/drivers/pinctrl/pinctrl-at91-pio4.c
+++ b/drivers/pinctrl/pinctrl-at91-pio4.c
@@ -1053,6 +1053,12 @@ static const struct atmel_pioctrl_data atmel_sama5d2_pioctrl_data = {
.last_bank_count = ATMEL_PIO_NPINS_PER_BANK,
};
+static const struct atmel_pioctrl_data microchip_sama7d65_pioctrl_data = {
+ .nbanks = 5,
+ .last_bank_count = 14, /* sama7d65 has only PE0 to PE13 */
+ .slew_rate_support = 1,
+};
+
static const struct atmel_pioctrl_data microchip_sama7g5_pioctrl_data = {
.nbanks = 5,
.last_bank_count = 8, /* sama7g5 has only PE0 to PE7 */
@@ -1063,6 +1069,9 @@ static const struct of_device_id atmel_pctrl_of_match[] = {
{
.compatible = "atmel,sama5d2-pinctrl",
.data = &atmel_sama5d2_pioctrl_data,
+ }, {
+ .compatible = "microchip,sama7d65-pinctrl",
+ .data = µchip_sama7d65_pioctrl_data,
}, {
.compatible = "microchip,sama7g5-pinctrl",
.data = µchip_sama7g5_pioctrl_data,
--
2.43.0
next reply other threads:[~2026-01-05 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 9:59 nicolas.ferre [this message]
2026-01-07 14:22 ` 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=20260105095956.19615-1-nicolas.ferre@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Ryan.Wanner@microchip.com \
--cc=brgl@bgdev.pl \
--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®