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,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/4] arm64: dts: renesas: salvator-x(s): Factor out common optional parts
Date: Mon, 7 Jun 2021 19:39:01 +0200 [thread overview]
Message-ID: <cover.1623087028.git.geert+renesas@glider.be> (raw)
Hi all,
The Renesas Salvator-X(S) family of boards are available with different
SiP options (R-Car H3 ES1.x, H3 ES2.0+, M3-W, M3-W+, M3-N). To reduce
duplication of board descriptions, the parts common to all SoC and board
combinations are already factored out into salvator-common.dtsi,
salvator-x.dtsi, and salvator-xs.dtsi. Still, there are a few board
features that are not common to all combos, as the corresponding support
is not present on all SoCs.
Hence this patch series moves out support for the second HDMI channel,
the SATA interface, and the third and fourth USB channels to
salvator-common.dtsi and/or salvator-xs.dtsi. As these are not present
on all SoCs, its descriptions are protected by SOC_HAS_* preprocessor
symbols, defined in SoC-specific .dtsi files.
This series causes no changes in the generated DTB, except for the
enablement of the SATA device node on Salvator-X board with an R-Car
M3-N SiP, cfr. the comments in [PATCH 2/4].
Thanks for your comments!
Geert Uytterhoeven (4):
arm64: dts: renesas: salvator-x(s): Factor out HDMI1 parts
arm64: dts: renesas: salvator-x(s): Factor out SATA parts
arm64: dts: renesas: salvator-x(s): Factor out USB ch2 parts
arm64: dts: renesas: salvator-xs: Factor out USB ch3 parts
.../boot/dts/renesas/r8a77950-salvator-x.dts | 73 -----------
arch/arm64/boot/dts/renesas/r8a77950.dtsi | 2 +
.../boot/dts/renesas/r8a77951-salvator-x.dts | 73 -----------
.../boot/dts/renesas/r8a77951-salvator-xs.dts | 122 ------------------
arch/arm64/boot/dts/renesas/r8a77951.dtsi | 5 +
.../boot/dts/renesas/r8a77965-salvator-xs.dts | 14 --
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 2 +
.../boot/dts/renesas/salvator-common.dtsi | 76 ++++++++++-
arch/arm64/boot/dts/renesas/salvator-xs.dtsi | 56 ++++++++
9 files changed, 140 insertions(+), 283 deletions(-)
--
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-06-07 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 17:39 Geert Uytterhoeven [this message]
2021-06-07 17:39 ` [PATCH 1/4] arm64: dts: renesas: salvator-x(s): Factor out HDMI1 parts Geert Uytterhoeven
2021-06-07 17:39 ` [PATCH 2/4] arm64: dts: renesas: salvator-x(s): Factor out SATA parts Geert Uytterhoeven
2021-06-07 17:39 ` [PATCH 3/4] arm64: dts: renesas: salvator-x(s): Factor out USB ch2 parts Geert Uytterhoeven
2021-06-07 17:39 ` [PATCH 4/4] arm64: dts: renesas: salvator-xs: Factor out USB ch3 parts Geert Uytterhoeven
2021-06-08 11:17 ` [PATCH 0/4] arm64: dts: renesas: salvator-x(s): Factor out common optional parts Niklas Söderlund
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.1623087028.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 \
/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).