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/3] Renesas SoC updates for v6.14
Date: Fri, 20 Dec 2024 11:28:44 +0100	[thread overview]
Message-ID: <cover.1734689797.git.geert+renesas@glider.be> (raw)

	Hi SoC folks,

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

It consists of 3 parts:

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

    - Enable Watchdog support for the RZ/V2H(P) SoC and the RZ/V2H EVK
      board in the ARM64 defconfig,
    - Refresh shmobile_defconfig for v6.13-rc1,
    - Enable support for the Renesas RZ/G3E (R9A09G047) SoC in the ARM64
      defconfig.

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

    - Initial support for the Renesas RZ/G3E (R9A09G047) SoC.

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

    - Add more serial (SCIF), power monitor, ADC, and sound support for
      the RZ/G3S SoC and the RZ/G3S SMARC SoM and development board,
    - Add support for the R-Car V4H ES3.0 (R8A779G3) SoC on the White Hawk
      Single development board,
    - Add display support for the R-Car V4M SoC and the Gray Hawk Single
      development board,
    - Add video capture support for the Gray Hawk Single development
      board,
    - Add initial support for the RZ/G3E (R9A09G047) SoC and the RZ/G3E
      SMARC SoM and Carrier-II EVK development board,
    - Add support for 5-port MATEnet on the Falcon Ethernet sub-board,
    - Miscellaneous fixes and improvements.

Note that the third part includes DT bindings and binding definitions
for the RZ/G3E SoC, which are shared by DT source files and the clock
driver.

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:[~2024-12-20 10:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 10:28 Geert Uytterhoeven [this message]
2024-12-20 10:28 ` [GIT PULL 1/3] Renesas ARM defconfig updates for v6.14 Geert Uytterhoeven
2024-12-20 10:28 ` [GIT PULL 2/3] Renesas driver " Geert Uytterhoeven
2024-12-20 10:28 ` [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.1734689797.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