Linux SOC development
 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/4] Renesas SoC updates for v6.16
Date: Fri, 25 Apr 2025 14:34:55 +0200	[thread overview]
Message-ID: <cover.1745582587.git.geert+renesas@glider.be> (raw)

	Hi SoC folks,

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

It consists of 4 parts:

  [GIT PULL 1/4] Renesas ARM defconfig updates for v6.16

    - Enable all Renesas SoCs by default when ARCH_RENESAS is set, and
      remove individual SoC entries from the various defconfigs.

  [GIT PULL 2/4] Renesas driver updates for v6.16

    - Enable all Renesas SoCs by default when ARCH_RENESAS is set, which
      will allow up to remove all individual Renesas SoC entries from the
      various defconfigs,
    - Initial support for the Renesas RZ/V2N (R9A09G056) SoC.

  [GIT PULL 3/4] Renesas DT binding updates for v6.16

    - Document support for the Renesas RZ/T2H (R9A09G077) SoC and the
      RZT2H-EVK evaluation board,
    - Document support for the Retronix Sparrow Hawk board, which is based
      on R-Car V4H ES3.0.

  [GIT PULL 4/4] Renesas DTS updates for v6.16

    - Add SDHI, ICU, I2C, PMIC, and GPU support on the RZ/G3E SoC and the
      RZ/G3E SoM and SMARC Carrier-II EVK development board,
    - Add internal SDHI regulator support on the RZ/V2H(P) SoC,
    - Add UFS tuning parameters in E-FUSE on the R-Car S4-8 ES1.2 SoC,
    - Add support for Ethernet ports C and D, I2C, keys, and SDHI on the
      RZ/N1D SoC and the RZN1D-DB and RZN1D-EB development and expansion
      boards,
    - Add initial support for the RZ/V2N (R9A09G056) and the RZ/V2N EVK
      board,
    - Add support for the Retronix Sparrow Hawk board, which is based on
      R-Car V4H ES3.0,
    - Add ISP core support on R-Car V3U, V4H, and V4M,
    - Miscellaneous fixes and improvements.

Notes:
  - The commit "soc: renesas: Kconfig: Enable SoCs by default when
    ARCH_RENESAS is set" is shared by PRs 1/4 and 2/4, as the defconfig
    updates depend on it,
  - PR 4/4 includes DT bindings and bindings definitions for the RZ/V2N
    SoC, which are shared by DT source files and device drivers.

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-04-25 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25 12:34 Geert Uytterhoeven [this message]
2025-04-25 12:34 ` [GIT PULL 1/4] Renesas ARM defconfig updates for v6.16 Geert Uytterhoeven
2025-04-25 12:34 ` [GIT PULL 2/4] Renesas driver " Geert Uytterhoeven
2025-04-25 12:34 ` [GIT PULL 3/4] Renesas DT binding " Geert Uytterhoeven
2025-04-25 12:34 ` [GIT PULL 4/4] 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.1745582587.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