public inbox for linux-arm-kernel@lists.infradead.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/4] Renesas SoC updates for v7.1
Date: Fri, 13 Mar 2026 12:12:56 +0100	[thread overview]
Message-ID: <cover.1773399669.git.geert+renesas@glider.be> (raw)

	Hi SoC folks,

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

It consists of 4 parts:

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

    - Refresh the ARM SH-Mobile defconfig for v7.0-rc1.

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

    - Initial support for the Renesas RZ/G3L (R9A08G046) SoC.

  [GIT PULL 3/4] Renesas DT binding updates for v7.1

    - Document RZ/G3L SoC variants, the RZ/G3L SYSC block, and RZ/G3L
      SMARC SoM and Carrier-II EVK boards.

  [GIT PULL 4/4] Renesas DTS updates for v7.1

    - Add CPU frequency scaling and QSPI NOR FLASH support on the RZ/N1
      SoC and the RZN1D-DB development board,
    - Add PCIe slot power control on the R-Car H3, M3-W(+), M3-N, and E3
      SoCs,
    - Add USB3.0 PHY support on the R-Car E3 SoC and the Ebisu development
      board,
    - Add PCIe/USB3.0 clock generator support on the Salvator-X(S), ULCB
      King Fisher extension, and Ebisu development boards,
    - Add RTC support on the RZ/V2N SoC and its EVK board,
    - Add SPI DMA support on the RZ/T2H, RZ/N2H, RZ/V2H(P), and RZ/V2N
      SoCs,
    - Add support for the second SDHI channel on the Atmark Techno
      Armadillo-800-EVA board,
    - Miscellaneous fixes and improvements.

Note that the fourth PR is based on "[GIT PULL] Renesas SoC fixes for
v7.0".

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-03-13 11:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 11:12 Geert Uytterhoeven [this message]
2026-03-13 11:12 ` [GIT PULL 1/4] Renesas ARM defconfig updates for v7.1 Geert Uytterhoeven
2026-03-13 11:12 ` [GIT PULL 2/4] Renesas driver " Geert Uytterhoeven
2026-03-13 11:12 ` [GIT PULL 3/4] Renesas DT binding " Geert Uytterhoeven
2026-03-14 11:09   ` Krzysztof Kozlowski
2026-03-16  8:51     ` Geert Uytterhoeven
2026-03-17  9:29       ` Krzysztof Kozlowski
2026-03-17  9:53         ` Krzysztof Kozlowski
2026-03-18 12:58           ` Arnd Bergmann
2026-03-13 11:13 ` [GIT PULL 4/4] Renesas DTS " Geert Uytterhoeven
2026-03-14 11:13   ` Krzysztof Kozlowski
2026-03-16  8:15     ` Geert Uytterhoeven
2026-03-14 11:23   ` Krzysztof Kozlowski
2026-03-16  8:18     ` Geert Uytterhoeven
2026-03-16  8:22       ` Krzysztof Kozlowski
2026-03-16  8:25         ` Geert Uytterhoeven
2026-03-17  8:32 ` [GIT PULL 0/4] Renesas SoC " Krzysztof Kozlowski
2026-03-17  8:46   ` Geert Uytterhoeven
2026-03-17  9:11     ` Krzysztof Kozlowski
2026-03-18 12:56       ` Arnd Bergmann
2026-03-18 13:12         ` Arnd Bergmann

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.1773399669.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