From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [GIT PULL] pinctrl: renesas: Updates for v6.18
Date: Fri, 29 Aug 2025 14:18:46 +0200 [thread overview]
Message-ID: <cover.1756469283.git.geert+renesas@glider.be> (raw)
Hi Linus,
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git tags/renesas-pinctrl-for-v6.18-tag1
for you to fetch changes up to d1d31e2739ff063da1e85cd9b44316ca5cccdba8:
pinctrl: renesas: rzt2h: Add support for RZ/N2H (2025-08-20 08:56:15 +0200)
----------------------------------------------------------------
pinctrl: renesas: Updates for v6.18
- Add support for Output Enable (OEN) on RZ/G3E,
- Add support for the RZ/T2H and RZ/N2H SoCs,
- Miscellaneous fixes and improvements.
Note that this includes DT binding definition updates for the RZ/T2H and
RZ/N2H SoCs, which are shared by clock driver, pin control driver, and
DT source files.
Thanks for pulling!
----------------------------------------------------------------
Geert Uytterhoeven (1):
Merge tag 'renesas-r9a09g077-dt-binding-defs-tag3' into renesas-pinctrl-for-v6.18
Lad Prabhakar (10):
pinctrl: renesas: rzg2l: Fix invalid unsigned return in rzg3s_oen_read()
pinctrl: renesas: rzg2l: Parameterize OEN register offset
pinctrl: renesas: rzg2l: Unify OEN access by making pin-to-bit mapping configurable
pinctrl: renesas: rzg2l: Remove OEN ops for RZ/G3E
pinctrl: renesas: rzg2l: Unify OEN handling across RZ/{G2L,V2H,V2N}
pinctrl: renesas: rzg2l: Add PFC_OEN support for RZ/G3E SoC
pinctrl: renesas: rzg2l: Drop oen_read and oen_write callbacks
dt-bindings: clock: renesas,r9a09g077/87: Add USB_CLK clock ID
dt-bindings: pinctrl: renesas: Document RZ/T2H and RZ/N2H SoCs
pinctrl: renesas: rzt2h: Add support for RZ/N2H
Thierry Bultel (1):
pinctrl: renesas: Add support for RZ/T2H
.../pinctrl/renesas,r9a09g077-pinctrl.yaml | 172 +++++
drivers/pinctrl/renesas/Kconfig | 13 +
drivers/pinctrl/renesas/Makefile | 1 +
drivers/pinctrl/renesas/pinctrl-rzg2l.c | 195 +++--
drivers/pinctrl/renesas/pinctrl-rzt2h.c | 813 +++++++++++++++++++++
.../dt-bindings/clock/renesas,r9a09g077-cpg-mssr.h | 1 +
.../dt-bindings/clock/renesas,r9a09g087-cpg-mssr.h | 1 +
.../pinctrl/renesas,r9a09g077-pinctrl.h | 22 +
8 files changed, 1112 insertions(+), 106 deletions(-)
create mode 100644 Documentation/devicetree/bindings/pinctrl/renesas,r9a09g077-pinctrl.yaml
create mode 100644 drivers/pinctrl/renesas/pinctrl-rzt2h.c
create mode 100644 include/dt-bindings/pinctrl/renesas,r9a09g077-pinctrl.h
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2025-08-29 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 12:18 Geert Uytterhoeven [this message]
2025-08-29 22:35 ` [GIT PULL] pinctrl: renesas: Updates for v6.18 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=cover.1756469283.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@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;
as well as URLs for NNTP newsgroup(s).