public inbox for soc@kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: soc@lists.linux.dev, soc <soc@kernel.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [GIT PULL 0/3] Renesas SoC updates for v6.20
Date: Mon,  5 Jan 2026 16:57:37 +0100	[thread overview]
Message-ID: <cover.1767628163.git.geert+renesas@glider.be> (raw)

	Hi SoC folks,

This is my first pull request for the inclusion of Renesas SoC updates
for v6.20.

It consists of 3 parts:

  [GIT PULL 1/3] Renesas ARM defconfig updates for v6.20

    - Enable support for the Renesas RZ/G3E USB3 PHY and RZ/G3S PCIe
      drivers in the ARM64 defconfig,
    - Refresh the ARM SH-Mobile defconfig for v6.19-rc1.

  [GIT PULL 2/3] Renesas driver updates for v6.20

    - Enable Interrupt Controller (ICU) support on the RZ/N2H SoC.

  [GIT PULL 3/3] Renesas DTS updates for v6.20

    - Add USB3.2 host and more RSCI serial support for the RZ/G3E SoC and
      the RZ/G3E SMARC EVK board,
    - Add display and USB3.0 host support for the RZ/V2H and RZ/V2N SoCs
      and their EVK boards,
    - Add SPI NOR Flash support for the Yuridenki-Shokai Kakip board,
    - Add PCIe support for the RZ/G3S SoC and the RZ/G3S SMARC EVK board,
    - Add SPI, interrupt controller, and DMAC support for the RZ/T2H,
      RZ/N2H, and RZ/V2N SoCs,
    - Add NMI wakeup button support for the RZ/V2N EVK board,
    - Add thermal support for the RZ/V2N SoC,
    - Add system watchdog timer support for R-Car V3H, which is reserved
      for secure firmware,
    - Add window watchdog timer support for R-Car V3M, V3H, and Gen4 SoCs,
    - Miscellaneous fixes and improvements.

Thanks for pulling!

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-01-05 15:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05 15:57 Geert Uytterhoeven [this message]
2026-01-05 15:57 ` [GIT PULL 1/3] Renesas ARM defconfig updates for v6.20 Geert Uytterhoeven
2026-01-05 15:57 ` [GIT PULL 2/3] Renesas driver " Geert Uytterhoeven
2026-01-05 15:57 ` [GIT PULL 3/3] Renesas DTS " Geert Uytterhoeven
2026-01-07 17:47 ` [GIT PULL 0/3] Renesas SoC " patchwork-bot+linux-soc
2026-01-21 16:00 ` patchwork-bot+linux-soc

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.1767628163.git.geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=soc@kernel.org \
    --cc=soc@lists.linux.dev \
    /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