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/5] Renesas SoC updates for v6.15
Date: Fri, 21 Feb 2025 17:57:21 +0100 [thread overview]
Message-ID: <cover.1740156736.git.geert+renesas@glider.be> (raw)
Hi SoC folks,
This is my first pull request for the inclusion of Renesas SoC updates
for v6.15.
It consists of 5 parts:
[GIT PULL 1/5] Renesas ARM defconfig updates for v6.15
- Supplement DTB with ATAG information, for older boards.
[GIT PULL 2/5] Renesas ARM SoC updates for v6.15
- Remove the legacy CMA reservation code on R-Car Gen2, which causes
issues with highmem.
[GIT PULL 3/5] Renesas driver updates for v6.15
- Add a driver for the System Controller on RZ/G3S, RZ/G3E, and
RZ/V2H.
[GIT PULL 4/5] Renesas DT binding updates for v6.15
- Document support for the Yuridenki-Shokai Kakip (based on RZ/V2H)
and MYIR Remi Pi (based on RZ/G2L) boards,
- Document support for the RZ/G3E System Controller.
[GIT PULL 5/5] Renesas DTS updates for v6.15
- Add support for the second and third Ethernet interfaces on the Gray
Hawk Single development board,
- Add Image Signal Processor helper block (FCPVX and VSPX) support for
the R-Car V3U and V4M SoCs,
- Add Watchdog and System Controller support for the RZ/G3E SoC and
the RZ/G3E SMARC Carrier-II EVK development board,
- Add initial support for the Yuridenki-Shokai Kakip and MYIR Remi Pi
boards,
- Add support for the spare UART and PMOD serial ports on the RZ/G3S
SMARC Carrier II board,
- Add a CPU Operating Performance Points table for the RZ/G3S SoC,
- Add boot phase tags on R-Car Gen2/3/4 and RZ/G2 boards,
- 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
next reply other threads:[~2025-02-21 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 16:57 Geert Uytterhoeven [this message]
2025-02-21 16:57 ` [GIT PULL 1/5] Renesas ARM defconfig updates for v6.15 Geert Uytterhoeven
2025-02-21 16:57 ` [GIT PULL 2/5] Renesas ARM SoC " Geert Uytterhoeven
2025-02-21 16:57 ` [GIT PULL 3/5] Renesas driver " Geert Uytterhoeven
2025-02-21 16:57 ` [GIT PULL 4/5] Renesas DT binding " Geert Uytterhoeven
2025-02-21 16:57 ` [GIT PULL 5/5] 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.1740156736.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