From: Geert Uytterhoeven <geert+renesas@glider.be>
To: arm-soc <arm@kernel.org>, arm-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 1/4] Renesas ARM SoC updates for v5.10 (take two)
Date: Fri, 18 Sep 2020 14:47:56 +0200 [thread overview]
Message-ID: <20200918124800.15555-1-geert+renesas@glider.be> (raw)
Hi arm-soc folks,
This is my second pull request for the inclusion of Renesas SoC updates
for v5.10.
It consists of 4 parts:
[GIT PULL 1/4] Renesas ARM DT updates for v5.10 (take two)
- PCIe endpoint support for the RZ/G2H SoC,
- SATA support for the HopeRun HiHope RZ/G2H board,
- Increase support (CAN, LED, SPI NOR, VIN, VSP) for the RZ/G1H SoC on
the iWave Qseven board (G21D), and its camera add-on board,
- Initial support for the R-Car V3U SoC on the Falcon CPU and BreakOut
boards,
- HDMI display and sound support for the R-Car M3-W+ SoC on the
Salvator-XS board,
- Digital Radio Interface (DRIF) support for the R-Car E3 SoC,
- Minor fixes and cleanups.
[GIT PULL 2/4] Renesas ARM SoC updates for v5.10
- Make two local functions static.
[GIT PULL 3/4] Renesas driver updates for v5.10 (take two)
- Add core support for the R-Car V3U (R8A779A0) SoC, including System
Controller (SYSC) and Reset (RST) support,
- Various Kconfig cleanups.
[GIT PULL 4/4] Renesas DT binding updates for v5.10
- Document core support for the R-Car V3U (R8A779A0) SoC and the
Renesas Falcon CPU and BreakOut boards.
Note that the new Renesas R-Car V3U DT Binding Definitions are shared by
driver and DT source files, and thus included in multiple pull requests:
- "[GIT PULL] clk: renesas: Updates for v5.10 (take two)" (for clk),
- "[GIT PULL 1/4] Renesas ARM DT updates for v5.10 (take two)" (for
arm-soc),
- "[GIT PULL 3/4] Renesas driver updates for v5.10 (take two)" (for
arm-soc).
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:[~2020-09-18 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 12:47 Geert Uytterhoeven [this message]
2020-09-18 12:47 ` [GIT PULL 1/4] Renesas ARM DT updates for v5.10 (take two) Geert Uytterhoeven
2020-09-18 12:47 ` [GIT PULL 2/4] Renesas ARM SoC updates for v5.10 Geert Uytterhoeven
2020-09-18 12:47 ` [GIT PULL 3/4] Renesas driver updates for v5.10 (take two) Geert Uytterhoeven
2020-09-18 12:48 ` [GIT PULL 4/4] Renesas DT binding updates for v5.10 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=20200918124800.15555-1-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;
as well as URLs for NNTP newsgroup(s).