Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Linus Walleij <linusw@kernel.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 v7.4
Date: Fri, 18 Sep 2026 11:38:08 +0200	[thread overview]
Message-ID: <cover.1789723325.git.geert+renesas@glider.be> (raw)

	Hi Linus,

The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:

  Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git tags/renesas-pinctrl-for-v7.4-tag1

for you to fetch changes up to 0cd4a7b3a4883970df3ae8814d9aabdecf65a81e:

  pinctrl: renesas: rzt2h: Add a helper for reading PFC (2026-09-15 10:49:07 +0200)

----------------------------------------------------------------
pinctrl: renesas: Updates for v7.4

  - Add SD power source support on RZ/G3L,
  - Add I3C power source support on RZ/G3S,
  - Miscellaneous fixes and improvements.

Thanks for pulling!

----------------------------------------------------------------
Biju Das (1):
      pinctrl: renesas: rzg2l: Add SD channel POC support for RZ/G3L

Claudiu Beznea (5):
      pinctrl: renesas: rzg2l: Generalize power source code
      pinctrl: renesas: rzg2l: Drop defines present in struct rzg2l_hwcfg
      pinctrl: renesas: rzg2l: Unify power source handling
      dt-bindings: pinctrl: renesas,rzg2l-pinctrl: Document missing I3C power source option
      pinctrl: renesas: rzg2l: Add RZ/G3S support for selecting I3C power source

Cosmin Tanislav (8):
      pinctrl: renesas: rzt2h: Fix used_irqs indexing in clear path
      pinctrl: renesas: rzt2h: Wire up struct gpio_chip::set_config
      pinctrl: renesas: rzt2h: Remove unused struct rzt2h_pinctrl::gpio_range
      pinctrl: renesas: rzt2h: Restore correct pin mode on IRQ free
      pinctrl: renesas: rzt2h: Setup IRQ in .irq_{request,release}_resources()
      pinctrl: renesas: rzt2h: Fix reading pin value in IRQ function
      pinctrl: renesas: rzt2h: Reuse helpers
      pinctrl: renesas: rzt2h: Add a helper for reading PFC

Josua Mayer (1):
      dt-bindings: pinctrl: renesas,rzg2l-pinctrl: Allow input/output-disable

 .../bindings/pinctrl/renesas,rzg2l-pinctrl.yaml    |   4 +-
 drivers/pinctrl/renesas/pinctrl-rzg2l.c            | 410 ++++++++++++++-------
 drivers/pinctrl/renesas/pinctrl-rzt2h.c            | 182 +++++----
 3 files changed, 403 insertions(+), 193 deletions(-)

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

             reply	other threads:[~2026-09-18  9:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18  9:38 Geert Uytterhoeven [this message]
2026-09-18 17:02 ` [GIT PULL] pinctrl: renesas: Updates for v7.4 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.1789723325.git.geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=linusw@kernel.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