From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 00/10] arm64: renesas: Add support for R Car H3e 2G-and M3e-2G
Date: Mon, 19 Jul 2021 17:38:31 +0200 [thread overview]
Message-ID: <cover.1626708063.git.geert+renesas@glider.be> (raw)
Hi all,
The new R-Car Gen3e SoCs are different gradings of the existing R-Car
Gen3 SoCs. This series adds support for the first two members of the
family: R-Car H3e-2G (R8A779M1) and R-Car M3e-2G (R8A779M3), on the
Salvator-XS and ULCB (with and without Kingfisher) development boards.
Changes compared to v1[1]:
- Add Reviewed-by, Acked-by.
- Drop new fam_rcar_gen3e and soc_rcar_[hm]3e, just use the existing
soc_rcar_{h3,m3_w},
- Drop pinctrl fix, which has evolved independently[2],
- Drop mmc fix, which has been superseded by a recent refactoring[3],
- Drop 2 GHz turbo modes, as the official opp-microvolt values are not
yet available,
- Widen the audience.
This series has been tested on Salvator-X with R-Car H3 ES3.0 and
Salvator-XS with R-Car M3-W+. For testing, a branch with dependencies
and fixups to prototype R-Car Gen3e development on older Gen3 SoCs can
be found at[4].
I plan to queue this in renesas-devel for v5.15.
Thanks for your comments!
[1] "[PATCH 00/14] arm64: renesas: Add support for R-Car H3e 2G-and M3e-2G"
(https://lore.kernel.org/r/cover.1623315732.git.geert+renesas@glider.be/).
[2] "[PATCH v2] pinctrl: renesas: Fix pin control matching on R-Car H3e-2G"
(https://lore.kernel.org/r/6cdc5bfa424461105779b56f455387e03560cf66.1626707688.git.geert+renesas@glider.be)
[3] "[PATCH v3] mmc: host: renesas_sdhi: Refactor renesas_sdhi_probe()"
(https://lore.kernel.org/r/20210702112956.1065875-1-yoshihiro.shimoda.uh@renesas.com/)
[2] https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git/log/?h=topic/rcar-gen3e-v2
Geert Uytterhoeven (10):
dt-bindings: arm: renesas: Document R-Car H3e-2G and M3e-2G SoCs and
boards
soc: renesas: Identify R-Car H3e-2G and M3e-2G
arm64: dts: renesas: Add Renesas R8A779M1 SoC support
arm64: dts: renesas: Add Renesas R8A779M3 SoC support
arm64: dts: renesas: Add support for Salvator-XS with R-Car H3e-2G
arm64: dts: renesas: Add support for H3ULCB with R-Car H3e-2G
arm64: dts: renesas: Add support for H3ULCB+Kingfisher with R-Car
H3e-2G
arm64: dts: renesas: Add support for Salvator-XS with R-Car M3e-2G
arm64: dts: renesas: Add support for M3ULCB with R-Car M3e-2G
arm64: dts: renesas: Add support for M3ULCB+Kingfisher with R-Car
M3e-2G
.../devicetree/bindings/arm/renesas.yaml | 50 +++++++++++++----
arch/arm64/boot/dts/renesas/Makefile | 8 +++
.../boot/dts/renesas/r8a779m1-salvator-xs.dts | 53 ++++++++++++++++++
.../boot/dts/renesas/r8a779m1-ulcb-kf.dts | 19 +++++++
arch/arm64/boot/dts/renesas/r8a779m1-ulcb.dts | 54 +++++++++++++++++++
arch/arm64/boot/dts/renesas/r8a779m1.dtsi | 12 +++++
.../boot/dts/renesas/r8a779m3-salvator-xs.dts | 46 ++++++++++++++++
.../boot/dts/renesas/r8a779m3-ulcb-kf.dts | 18 +++++++
arch/arm64/boot/dts/renesas/r8a779m3-ulcb.dts | 45 ++++++++++++++++
arch/arm64/boot/dts/renesas/r8a779m3.dtsi | 12 +++++
drivers/soc/renesas/Kconfig | 2 +
drivers/soc/renesas/renesas-soc.c | 4 ++
12 files changed, 312 insertions(+), 11 deletions(-)
create mode 100644 arch/arm64/boot/dts/renesas/r8a779m1-salvator-xs.dts
create mode 100644 arch/arm64/boot/dts/renesas/r8a779m1-ulcb-kf.dts
create mode 100644 arch/arm64/boot/dts/renesas/r8a779m1-ulcb.dts
create mode 100644 arch/arm64/boot/dts/renesas/r8a779m1.dtsi
create mode 100644 arch/arm64/boot/dts/renesas/r8a779m3-salvator-xs.dts
create mode 100644 arch/arm64/boot/dts/renesas/r8a779m3-ulcb-kf.dts
create mode 100644 arch/arm64/boot/dts/renesas/r8a779m3-ulcb.dts
create mode 100644 arch/arm64/boot/dts/renesas/r8a779m3.dtsi
--
2.25.1
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:[~2021-07-19 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 15:38 Geert Uytterhoeven [this message]
2021-07-19 15:38 ` [PATCH v2 01/10] dt-bindings: arm: renesas: Document R-Car H3e-2G and M3e-2G SoCs and boards Geert Uytterhoeven
2021-07-19 15:38 ` [PATCH v2 02/10] soc: renesas: Identify R-Car H3e-2G and M3e-2G Geert Uytterhoeven
2021-07-19 15:38 ` [PATCH v2 03/10] arm64: dts: renesas: Add Renesas R8A779M1 SoC support Geert Uytterhoeven
2021-07-19 15:38 ` [PATCH v2 04/10] arm64: dts: renesas: Add Renesas R8A779M3 " Geert Uytterhoeven
2021-07-19 15:38 ` [PATCH v2 05/10] arm64: dts: renesas: Add support for Salvator-XS with R-Car H3e-2G Geert Uytterhoeven
2021-07-19 15:38 ` [PATCH v2 06/10] arm64: dts: renesas: Add support for H3ULCB " Geert Uytterhoeven
2021-07-19 15:38 ` [PATCH v2 07/10] arm64: dts: renesas: Add support for H3ULCB+Kingfisher " Geert Uytterhoeven
2021-07-19 15:38 ` [PATCH v2 08/10] arm64: dts: renesas: Add support for Salvator-XS with R-Car M3e-2G Geert Uytterhoeven
2021-07-19 15:38 ` [PATCH v2 09/10] arm64: dts: renesas: Add support for M3ULCB " Geert Uytterhoeven
2021-07-19 15:38 ` [PATCH v2 10/10] arm64: dts: renesas: Add support for M3ULCB+Kingfisher " 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.1626708063.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).