From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 0/9] arm64: dts: renesas: Add support for more R-Car V4H and White Hawk variants
Date: Thu, 25 Jan 2024 15:48:50 +0100 [thread overview]
Message-ID: <cover.1706192990.git.geert+renesas@glider.be> (raw)
Hi all,
This patch series extends the existing support for the Renesas White
Hawk CPU and Breakout board stack by adding support for:
1. Standalone use of the White Hawk CPU board,
2. The White Hawk Single board, which is a single-board integration
of the Renesas White Hawk CPU and Breakout board stack, based on
the R-Car V4H ES2.0 (R8A779G2) SoC.
Changes compared to v1[1]:
- Add Reviewed-by.
- Split off restoring sort order into its own patch,
- New patch "[PATCH v2 5/9] arm64: dts: renesas: white-hawk: Add SoC
name to top-level comment",
- Rebase on top of commit fc67495680f60e88 ("arm64: dts: renesas:
white-hawk-cpu: Fix missing serial console pin control",
- Refer to hscif0_pins directly,
- Add SoC name to top-level comment.
I plan to queue this in renesas-devel for v6.9.
For testing, this series can be found at
https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git/log/?h=topic/v4h-white-hawk-more-v2
Thanks for your comments!
[1] "[PATCH/RFC 0/7] arm64: dts: renesas: Add support for more R-Car V4H and
White Hawk variants"
https://lore.kernel.org/linux-renesas-soc/cover.1702309604.git.geert+renesas@glider.be
Geert Uytterhoeven (9):
dt-bindings: soc: renesas: Document R-Car V4H White Hawk Single
arm64: dts: renesas: r8a779g0: Add standalone White Hawk CPU support
arm64: dts: renesas: white-hawk-cpu: Restore sort order
arm64: dts: renesas: white-hawk: Drop SoC parts from sub boards
arm64: dts: renesas: white-hawk: Add SoC name to top-level comment
arm64: dts: renesas: white-hawk-cpu: Factor out common parts
arm64: dts: renesas: white-hawk: Factor out common parts
arm64: dts: renesas: Add Renesas R8A779G2 SoC support
arm64: dts: renesas: r8a779g2: Add White Hawk Single support
.../bindings/soc/renesas/renesas.yaml | 7 +
arch/arm64/boot/dts/renesas/Makefile | 3 +
.../dts/renesas/r8a779g0-white-hawk-cpu.dts | 13 +
.../dts/renesas/r8a779g0-white-hawk-cpu.dtsi | 368 +-----------------
.../boot/dts/renesas/r8a779g0-white-hawk.dts | 58 +--
.../renesas/r8a779g2-white-hawk-single.dts | 26 ++
arch/arm64/boot/dts/renesas/r8a779g2.dtsi | 12 +
...-white-hawk.dts => white-hawk-common.dtsi} | 12 +-
...wk-cpu.dtsi => white-hawk-cpu-common.dtsi} | 21 +-
...k-csi-dsi.dtsi => white-hawk-csi-dsi.dtsi} | 2 +-
...ethernet.dtsi => white-hawk-ethernet.dtsi} | 2 +-
11 files changed, 80 insertions(+), 444 deletions(-)
create mode 100644 arch/arm64/boot/dts/renesas/r8a779g0-white-hawk-cpu.dts
create mode 100644 arch/arm64/boot/dts/renesas/r8a779g2-white-hawk-single.dts
create mode 100644 arch/arm64/boot/dts/renesas/r8a779g2.dtsi
copy arch/arm64/boot/dts/renesas/{r8a779g0-white-hawk.dts => white-hawk-common.dtsi} (71%)
copy arch/arm64/boot/dts/renesas/{r8a779g0-white-hawk-cpu.dtsi => white-hawk-cpu-common.dtsi} (97%)
rename arch/arm64/boot/dts/renesas/{r8a779g0-white-hawk-csi-dsi.dtsi => white-hawk-csi-dsi.dtsi} (97%)
rename arch/arm64/boot/dts/renesas/{r8a779g0-white-hawk-ethernet.dtsi => white-hawk-ethernet.dtsi} (76%)
--
2.34.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:[~2024-01-25 14:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 14:48 Geert Uytterhoeven [this message]
2024-01-25 14:48 ` [PATCH v2 1/9] dt-bindings: soc: renesas: Document R-Car V4H White Hawk Single Geert Uytterhoeven
2024-01-25 16:45 ` Conor Dooley
2024-01-25 14:48 ` [PATCH v2 2/9] arm64: dts: renesas: r8a779g0: Add standalone White Hawk CPU support Geert Uytterhoeven
2024-01-25 14:48 ` [PATCH v2 3/9] arm64: dts: renesas: white-hawk-cpu: Restore sort order Geert Uytterhoeven
2024-01-26 11:05 ` Wolfram Sang
2024-01-26 11:07 ` Geert Uytterhoeven
2024-01-25 14:48 ` [PATCH v2 4/9] arm64: dts: renesas: white-hawk: Drop SoC parts from sub boards Geert Uytterhoeven
2024-01-25 14:48 ` [PATCH v2 5/9] arm64: dts: renesas: white-hawk: Add SoC name to top-level comment Geert Uytterhoeven
2024-01-26 11:06 ` Wolfram Sang
2024-01-25 14:48 ` [PATCH v2 6/9] arm64: dts: renesas: white-hawk-cpu: Factor out common parts Geert Uytterhoeven
2024-01-26 11:07 ` Wolfram Sang
2024-01-25 14:48 ` [PATCH v2 7/9] arm64: dts: renesas: white-hawk: " Geert Uytterhoeven
2024-01-25 14:48 ` [PATCH v2 8/9] arm64: dts: renesas: Add Renesas R8A779G2 SoC support Geert Uytterhoeven
2024-01-25 14:48 ` [PATCH v2 9/9] arm64: dts: renesas: r8a779g2: Add White Hawk Single support 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.1706192990.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@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).