linux-arm-kernel.lists.infradead.org archive mirror
 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.19
Date: Fri, 31 Oct 2025 11:43:29 +0100	[thread overview]
Message-ID: <cover.1761905410.git.geert+renesas@glider.be> (raw)

	Hi SoC folks,

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

It consists of 3 parts:

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

    - Enable support for the Renesas RZ/G3S and RZ/G3E thermal drivers,
      and the RZ/T2H and RZ/N2H ADC drivers in the ARM64 defconfig,
    - Refresh the ARM SH-Mobile defconfig for v6.18-rc1.

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

    - Keep the WDTRSTCR.RESBAR2S bit in the default state on R-Car Gen4.

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

    - Add thermal support for the RZ/G3S and RZ/G3E SoCs,
    - Add DT overlay support for the Raspberry Pi Display 2 and Argon40
      fan hats on the Retronix Sparrow Hawk board,
    - Add eMMC support for the Eagle Function expansion board,
    - Add initial support for the R-Car X5H (R8A78000) SoC and the
      Ironhide development board,
    - Move interrupt-parent properties to root nodes,
    - Add system watchdog timer support for R-Car Gen3 and Gen4 SoCs,
      which is reserved for secure firmware on R-Car Gen3 boards,
    - Add ADC support for the RZ/T2H and RZ/N2H SoCs and their evaluation
      boards,
    - Add watchdog timer support on the R-Car V3M Starter Kit board,
    - Add Cortex-A55 PMU support on the RZ/V2H, RZ/V2N, RZ/T2H, and RZ/N2H
      SoCs,
    - Add Imagination Technologies PowerVR Series 6XT GX6250 GPU support
      on the R-Car M3-W and M3-W+ 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:[~2025-10-31 10:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31 10:43 Geert Uytterhoeven [this message]
2025-10-31 10:43 ` [GIT PULL 1/3] Renesas ARM defconfig updates for v6.19 Geert Uytterhoeven
2025-10-31 10:43 ` [GIT PULL 2/3] Renesas driver " Geert Uytterhoeven
2025-10-31 10:43 ` [GIT PULL 3/3] Renesas DTS " Geert Uytterhoeven

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.1761905410.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;
as well as URLs for NNTP newsgroup(s).