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 1/4] arm64: dts: rockchip: move rk3568 dtsi to rk356x dtsi
Date: Sat, 10 Jul 2021 11:10:31 -0400 [thread overview]
Message-ID: <20210710151034.32857-2-pgwipeout@gmail.com> (raw)
In-Reply-To: <20210710151034.32857-1-pgwipeout@gmail.com>
In preparation for separating the rk3568 and rk3566 device trees, move
the base rk3568 dtsi to rk356x dtsi.
This will allow us to strip out the rk3568 specific nodes.
Signed-off-by: Peter Geis <pgwipeout@gmail.com>
---
arch/arm64/boot/dts/rockchip/{rk3568.dtsi => rk356x.dtsi} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename arch/arm64/boot/dts/rockchip/{rk3568.dtsi => rk356x.dtsi} (100%)
diff --git a/arch/arm64/boot/dts/rockchip/rk3568.dtsi b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
similarity index 100%
rename from arch/arm64/boot/dts/rockchip/rk3568.dtsi
rename to arch/arm64/boot/dts/rockchip/rk356x.dtsi
--
2.25.1
WARNING: multiple messages have this Message-ID (diff)
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 1/4] arm64: dts: rockchip: move rk3568 dtsi to rk356x dtsi
Date: Sat, 10 Jul 2021 11:10:31 -0400 [thread overview]
Message-ID: <20210710151034.32857-2-pgwipeout@gmail.com> (raw)
In-Reply-To: <20210710151034.32857-1-pgwipeout@gmail.com>
In preparation for separating the rk3568 and rk3566 device trees, move
the base rk3568 dtsi to rk356x dtsi.
This will allow us to strip out the rk3568 specific nodes.
Signed-off-by: Peter Geis <pgwipeout@gmail.com>
---
arch/arm64/boot/dts/rockchip/{rk3568.dtsi => rk356x.dtsi} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename arch/arm64/boot/dts/rockchip/{rk3568.dtsi => rk356x.dtsi} (100%)
diff --git a/arch/arm64/boot/dts/rockchip/rk3568.dtsi b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
similarity index 100%
rename from arch/arm64/boot/dts/rockchip/rk3568.dtsi
rename to arch/arm64/boot/dts/rockchip/rk356x.dtsi
--
2.25.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
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 1/4] arm64: dts: rockchip: move rk3568 dtsi to rk356x dtsi
Date: Sat, 10 Jul 2021 11:10:31 -0400 [thread overview]
Message-ID: <20210710151034.32857-2-pgwipeout@gmail.com> (raw)
In-Reply-To: <20210710151034.32857-1-pgwipeout@gmail.com>
In preparation for separating the rk3568 and rk3566 device trees, move
the base rk3568 dtsi to rk356x dtsi.
This will allow us to strip out the rk3568 specific nodes.
Signed-off-by: Peter Geis <pgwipeout@gmail.com>
---
arch/arm64/boot/dts/rockchip/{rk3568.dtsi => rk356x.dtsi} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename arch/arm64/boot/dts/rockchip/{rk3568.dtsi => rk356x.dtsi} (100%)
diff --git a/arch/arm64/boot/dts/rockchip/rk3568.dtsi b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
similarity index 100%
rename from arch/arm64/boot/dts/rockchip/rk3568.dtsi
rename to arch/arm64/boot/dts/rockchip/rk356x.dtsi
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-10 15:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 15:10 [RFC PATCH 0/4] split rk3568 and rk3566 device trees Peter Geis
2021-07-10 15:10 ` Peter Geis
2021-07-10 15:10 ` Peter Geis
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 ` 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 ` Peter Geis
2021-07-10 15:10 ` Peter Geis
2021-07-10 15:10 ` [RFC PATCH 3/4] arm64: dts: rockchip: add rk3566 dtsi Peter Geis
2021-07-10 15:10 ` Peter Geis
2021-07-10 15:10 ` 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-10 15:10 ` Peter Geis
2021-07-10 15:10 ` Peter Geis
2021-07-15 16:21 ` Rob Herring
2021-07-15 16:21 ` Rob Herring
2021-07-15 16:21 ` Rob Herring
2021-07-20 16:19 ` Peter Geis
2021-07-20 16:19 ` Peter Geis
2021-07-20 16:19 ` Peter Geis
2021-07-28 17:25 ` Rob Herring
2021-07-28 17:25 ` Rob Herring
2021-07-28 17:25 ` Rob Herring
2021-07-23 12:02 ` [RFC PATCH 0/4] split rk3568 and rk3566 device trees Heiko Stuebner
2021-07-23 12:02 ` Heiko Stuebner
2021-07-23 12:02 ` 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-2-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.