From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: devicetree@vger.kernel.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH v2 0/6] arm64: dts: renesas: move I2C aliases to board files
Date: Thu, 25 Aug 2022 09:10:16 +0200 [thread overview]
Message-ID: <20220825071022.7864-1-wsa+renesas@sang-engineering.com> (raw)
Change since v1:
* converted r8a774a1 boards, too (Thanks, Geert!)
Old coverletter follows:
For R-Car Gen3 and Gen4, we had I2C aliases in per-SoC DTS include
files. That doesn't really fit as bus naming is a board property. This
series moves the aliases to the board files. The following procedure has
been applied to avoid regressions:
1) move the aliases from SoC files to board files. Keep the empty
alias-nodes in the SoC file and add the new aliases before existing
ones. This ensured that identical binaries[1] were created.
2) Once all aliases were moved and all binaries[1] stayed identical,
then the empty alias nodes from the SoC files were removed.
The result is this series based on the renesas-drivers tag
'renesas-drivers-2022-08-16-v6.0-rc1'.
It could be discussed if the aliases should be sorted alphabetically,
but I'd think this is a seperate series then.
I also leave it to Geert, if the commits should be squashed. At least
for reviewing, I think this separation makes sense, though.
Looking forward to comments,
Wolfram
[1] For desired binaries, of course. For r8a77961 boards, the binaries
did change. This was intended, though, because I wanted to add I2C
aliases there which were not present before. Also, the r8a779m* boards
now have I2C aliases, too.
Wolfram Sang (6):
arm64: dts: renesas: r8a779{51|60|65}: put I2C aliases to board files
arm64: dts: renesas: r8a77970: put I2C aliases to board files
arm64: dts: renesas: r8a77980: put I2C aliases to board files
arm64: dts: renesas: r8a77990: put I2C aliases to board files
arm64: dts: renesas: r8a779a0: put I2C aliases to board files
arm64: dts: renesas: r8a774a1: put I2C aliases to board files
arch/arm64/boot/dts/renesas/ebisu.dtsi | 8 ++++++++
arch/arm64/boot/dts/renesas/hihope-common.dtsi | 8 ++++++++
.../boot/dts/renesas/r8a774a1-beacon-rzg2m-kit.dts | 8 ++++++++
arch/arm64/boot/dts/renesas/r8a774a1.dtsi | 11 -----------
arch/arm64/boot/dts/renesas/r8a77951.dtsi | 11 -----------
arch/arm64/boot/dts/renesas/r8a77960.dtsi | 11 -----------
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 11 -----------
arch/arm64/boot/dts/renesas/r8a77970-eagle.dts | 5 +++++
arch/arm64/boot/dts/renesas/r8a77970-v3msk.dts | 5 +++++
arch/arm64/boot/dts/renesas/r8a77970.dtsi | 8 --------
arch/arm64/boot/dts/renesas/r8a77980-condor.dts | 6 ++++++
arch/arm64/boot/dts/renesas/r8a77980-v3hsk.dts | 6 ++++++
arch/arm64/boot/dts/renesas/r8a77980.dtsi | 9 ---------
arch/arm64/boot/dts/renesas/r8a77990.dtsi | 11 -----------
arch/arm64/boot/dts/renesas/r8a779a0-falcon-cpu.dtsi | 7 +++++++
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 10 ----------
arch/arm64/boot/dts/renesas/salvator-common.dtsi | 8 ++++++++
arch/arm64/boot/dts/renesas/ulcb.dtsi | 8 ++++++++
18 files changed, 69 insertions(+), 82 deletions(-)
--
2.35.1
next reply other threads:[~2022-08-25 7:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 7:10 Wolfram Sang [this message]
2022-08-25 7:10 ` [PATCH v2 1/6] arm64: dts: renesas: r8a779{51|60|65}: put I2C aliases to board files Wolfram Sang
2022-08-25 7:10 ` [PATCH v2 2/6] arm64: dts: renesas: r8a77970: " Wolfram Sang
2022-08-25 7:10 ` [PATCH v2 3/6] arm64: dts: renesas: r8a77980: " Wolfram Sang
2022-08-25 7:10 ` [PATCH v2 4/6] arm64: dts: renesas: r8a77990: " Wolfram Sang
2022-08-25 7:10 ` [PATCH v2 5/6] arm64: dts: renesas: r8a779a0: " Wolfram Sang
2022-08-25 7:10 ` [PATCH v2 6/6] arm64: dts: renesas: r8a774a1: " Wolfram Sang
2022-08-26 14:51 ` Geert Uytterhoeven
2022-08-26 14:54 ` [PATCH v2 0/6] arm64: dts: renesas: move " 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=20220825071022.7864-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-renesas-soc@vger.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).