From: FUKAUMI Naoki <naoki@radxa.com>
To: heiko@sntech.de
Cc: robh@kernel.org, conor+dt@kernel.org, inindev@gmail.com,
liujianfeng1994@gmail.com, jonas@kwiboo.se, dmt.yashin@gmail.com,
sebastian.reichel@collabora.com, tim@feathertop.org,
kever.yang@rock-chips.com, marcin.juszkiewicz@linaro.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
alchark@gmail.com, michael.riesch@wolfvision.net,
macromorgan@hotmail.com, FUKAUMI Naoki <naoki@radxa.com>,
krzk+dt@kernel.org, dsimic@manjaro.org
Subject: [PATCH 0/3] arm64: dts: rockchip: Add Radxa ROCK 5B+ and rebase Radxa ROCK 5B
Date: Tue, 24 Dec 2024 21:09:09 +0000 [thread overview]
Message-ID: <20241224210912.2121-1-naoki@radxa.com> (raw)
The Radxa ROCK 5B+ is an upgraded version of the Radxa ROCK 5B.
This patch series introduces a shared .dtsi that can be used on the
new Radxa ROCK 5B+, the existing Radxa ROCK 5B, and the upcoming Radxa
ROCK 5T.
This patch series includes "arm64: dts: rockchip: Add USB-C support to
ROCK 5B" by Sebastian Reichel[1].
[1] https://patchwork.kernel.org/project/linux-rockchip/patch/20241210163615.120594-1-sebastian.reichel@collabora.com/
FUKAUMI Naoki (3):
dt-bindings: arm: rockchip: Add Radxa ROCK 5B+
arm64: dts: rockchip: Add Radxa ROCK 5B+
arm64: dts: rockchip: Convert Radxa ROCK 5B to use shared .dtsi
.../devicetree/bindings/arm/rockchip.yaml | 5 +
arch/arm64/boot/dts/rockchip/Makefile | 1 +
...{rk3588-rock-5b.dts => rk3588-rock-5.dtsi} | 555 +++++----
.../boot/dts/rockchip/rk3588-rock-5b-plus.dts | 97 ++
.../boot/dts/rockchip/rk3588-rock-5b.dts | 1026 ++---------------
5 files changed, 549 insertions(+), 1135 deletions(-)
copy arch/arm64/boot/dts/rockchip/{rk3588-rock-5b.dts => rk3588-rock-5.dtsi} (71%)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3588-rock-5b-plus.dts
rewrite arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts (93%)
--
2.43.0
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2024-12-24 21:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 21:09 FUKAUMI Naoki [this message]
2024-12-24 21:09 ` [PATCH 1/3] dt-bindings: arm: rockchip: Add Radxa ROCK 5B+ FUKAUMI Naoki
2024-12-24 21:09 ` [PATCH 2/3] arm64: dts: " FUKAUMI Naoki
2024-12-24 21:09 ` [PATCH 3/3] arm64: dts: rockchip: Convert Radxa ROCK 5B to use shared .dtsi FUKAUMI Naoki
2024-12-25 8:32 ` [PATCH 0/3] arm64: dts: rockchip: Add Radxa ROCK 5B+ and rebase Radxa ROCK 5B Alexey Charkov
2024-12-25 9:35 ` Dragan Simic
2024-12-25 10:09 ` FUKAUMI Naoki
2024-12-25 10:25 ` Dragan Simic
2024-12-26 0:41 ` FUKAUMI Naoki
2024-12-27 15:18 ` Rob Herring (Arm)
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=20241224210912.2121-1-naoki@radxa.com \
--to=naoki@radxa.com \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmt.yashin@gmail.com \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=inindev@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=liujianfeng1994@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=michael.riesch@wolfvision.net \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=tim@feathertop.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