Linux-ARM-Kernel Archive on lore.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/2] Renesas SoC updates for v7.2
Date: Tue, 19 May 2026 12:35:57 +0200	[thread overview]
Message-ID: <cover.1779185457.git.geert+renesas@glider.be> (raw)

	Hi SoC folks,

This is my first pull request for the inclusion of Renesas SoC updates
for v7.2.

It consists of 2 parts:

  [GIT PULL 1/2] Renesas driver updates for v7.2

    - Add Multifunctional Interface (MFIS) mailbox and product register
      support for R-Car X5H,
    - Miscellaneous fixes and improvements.

  [GIT PULL 2/2] Renesas DTS updates for v7.2

    - Add GPU support for R-Car M3-W(+)-based ULCB and Salvator-X(S)
      development boards,
    - Add Ethernet, OPP table, interrupt, pin control, and watchdog
      support for the RZ/G3L SoC and the RZ/G3L SMARC SoM board,
    - Add Coresight support for the R-Mobile A1 and APE6 SoCs, and the
      Armadillo-800 EVA and APE6EVM development boards,
    - Miscellaneous fixes and improvements.

Note that the first PR includes DT binding definitions for R-Car X5H,
which are shared by driver and DT source files.

Note that the second PR (1) is based on v7.1-rc3, as PowerVR GPU
enablement has a dependency on commit 26735dfdd8930d9e ("pmdomain: core:
Fix detach procedure for virtual devices in genpd"), and (2) includes:
  - Renesas SoC fixes for v7.1, which are already present in
    soc/for-next, but not yet in v7.1-rc4,
  - DT binding definition updates for the R-Mobile A1 and APE6 SoCs,
    which are shared by the clock subsystem and DT source files,
  - DT binding definitions for the RZ/G3L SoC, which are shared by the
    pin control subsystem and DT source files.

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-05-19 10:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 10:35 Geert Uytterhoeven [this message]
2026-05-19 10:35 ` [GIT PULL 1/2] Renesas driver updates for v7.2 Geert Uytterhoeven
2026-05-19 10:35 ` [GIT PULL 2/2] 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.1779185457.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