From: Geert Uytterhoeven <geert+renesas@glider.be>
To: arm-soc <arm@kernel.org>, 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 v6.8
Date: Fri, 1 Dec 2023 13:28:15 +0100 [thread overview]
Message-ID: <cover.1701433485.git.geert+renesas@glider.be> (raw)
Hi SoC folks,
This is my first pull request for the inclusion of Renesas SoC updates
for v6.8.
It consists of 2 parts:
[GIT PULL 1/2] Renesas ARM defconfig updates for v6.8
- Enable support for the Renesas VersaClock 3 clock generator in the
arm64 defconfig,
- Enable support for the Renesas EtherAVB module in the arm multi_v7
defconfig,
- Refresh shmobile_defconfig for v6.7-rc1.
[GIT PULL 2/2] Renesas DTS updates for v6.8
- Add FLASH support for the Renesas Marzen and Blanche development
boards,
- Add 4-bit TX support for the QSPI FLASHes on the RZ/G2L, RZ/G2LC,
and RZ/V2L SMARC SoMs,
- Add SDHI support for the RZ/G3S SMARC development kit,
- Add LCD support for the Atmark Techno Armadillo-800-EVA development
board, which requires switching from the legacy frame buffer device
driver to the DRM driver,
- 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:[~2023-12-01 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 12:28 Geert Uytterhoeven [this message]
2023-12-01 12:28 ` [GIT PULL 1/2] Renesas ARM defconfig updates for v6.8 Geert Uytterhoeven
2023-12-01 12:28 ` [GIT PULL 2/2] Renesas DTS " Geert Uytterhoeven
2023-12-06 17:17 ` [GIT PULL 0/2] Renesas SoC " patchwork-bot+linux-soc
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.1701433485.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=soc@kernel.org \
/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