From: Peter Geis <pgwipeout@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>, Liang Chen <cl@rock-chips.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Peter Geis <pgwipeout@gmail.com>
Subject: [RFC PATCH 0/4] split rk3568 and rk3566 device trees
Date: Sat, 10 Jul 2021 11:10:30 -0400 [thread overview]
Message-ID: <20210710151034.32857-1-pgwipeout@gmail.com> (raw)
This is an example patch set that addresses the split of the rk3568 and
rk3566 soc device trees.
This method attempts to avoid deleting and modifing nodes by maintaining
a common dtsi for all common items and adding in the differences in
separate dtsi files.
It also includes a basic dts for the Pine64 Quartz64 Model A board
as an example of a rk3566 device.
This series has the following prerequisite:
arm64: dts: rockchip: add pmu and qos nodes for rk3568
https://patchwork.kernel.org/project/linux-rockchip/patch/20210624114719.1685-4-cl@rock-chips.com/
Peter Geis (4):
arm64: dts: rockchip: move rk3568 dtsi to rk356x dtsi
arm64: dts: rockchip: split rk3568 device tree
arm64: dts: rockchip: add rk3566 dtsi
arm64: dts: rockchip: add basic dts for Pine64 Quartz64-A
.../devicetree/bindings/arm/rockchip.yaml | 5 +
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../boot/dts/rockchip/rk3566-quartz64-a.dts | 321 +++++++
arch/arm64/boot/dts/rockchip/rk3566.dtsi | 20 +
arch/arm64/boot/dts/rockchip/rk3568.dtsi | 814 +-----------------
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 786 +++++++++++++++++
6 files changed, 1153 insertions(+), 794 deletions(-)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.dts
create mode 100644 arch/arm64/boot/dts/rockchip/rk3566.dtsi
create mode 100644 arch/arm64/boot/dts/rockchip/rk356x.dtsi
--
2.25.1
next reply other threads:[~2021-07-10 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 15:10 Peter Geis [this message]
2021-07-10 15:10 ` [RFC PATCH 1/4] arm64: dts: rockchip: move rk3568 dtsi to rk356x dtsi Peter Geis
2021-07-10 15:10 ` [RFC PATCH 2/4] arm64: dts: rockchip: split rk3568 device tree Peter Geis
2021-07-10 15:10 ` [RFC PATCH 3/4] arm64: dts: rockchip: add rk3566 dtsi Peter Geis
2021-07-10 15:10 ` [RFC PATCH 4/4] arm64: dts: rockchip: add basic dts for Pine64 Quartz64-A Peter Geis
2021-07-15 16:21 ` Rob Herring
2021-07-20 16:19 ` Peter Geis
2021-07-28 17:25 ` Rob Herring
2021-07-23 12:02 ` [RFC PATCH 0/4] split rk3568 and rk3566 device trees Heiko Stuebner
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=20210710151034.32857-1-pgwipeout@gmail.com \
--to=pgwipeout@gmail.com \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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).