From: "Heiko Stübner" <heiko@sntech.de>
To: zhao xinchao <ChrisXinchao@outlook.com>
Cc: "linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: rockchip: add Firefly AIO-3588L board
Date: Sun, 28 Jun 2026 15:09:48 +0200 [thread overview]
Message-ID: <2969865.Y6S9NjorxK@diego> (raw)
In-Reply-To: <SA0PR19MB4572AB455CF87D8BB3CFEE6EC5E92@SA0PR19MB4572.namprd19.prod.outlook.com>
Am Sonntag, 28. Juni 2026, 02:52:37 Mitteleuropäische Sommerzeit schrieb zhao xinchao:
> From: Chris Xin <chrisxinchao@outlook.com>
> Date: Sun, 28 Jun 2026 00:00:00 +0800
> Subject: [PATCH] arm64: dts: rockchip: add Firefly AIO-3588L board
>
> Add device tree for the Firefly AIO-3588L board based on the Rockchip
> RK3588 SoC. The board features:
> - Dual HDMI output via DesignWare HDMI QP
> - RTL8852BE WiFi on PCIe (rtw89 driver)
> - RTL8211F Ethernet
> - Single RK806 PMIC
> - LPDDR4 RAM, eMMC storage, USB 3.0
>
> The board DTS includes the common firefly-core-3588j.dtsi which provides
> PMIC, eMMC, and other shared configurations for Firefly RK3588 boards.
>
> Signed-off-by: Chris Xin <chrisxinchao@outlook.com>
> ---
> arch/arm64/boot/dts/rockchip/Makefile | 1 +
> .../boot/dts/rockchip/rk3588-firefly-aio-3588l.dts | 718 +++++++++++++++
> .../boot/dts/rockchip/rk3588-firefly-core-3588j.dtsi | 453 +++++++++
This is one patch, but where is the 2nd patch add the board binding?
Heiko
prev parent reply other threads:[~2026-06-28 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 0:52 [PATCH] arm64: dts: rockchip: add Firefly AIO-3588L board zhao xinchao
2026-06-28 8:46 ` Krzysztof Kozlowski
2026-06-28 13:09 ` Heiko Stübner [this message]
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=2969865.Y6S9NjorxK@diego \
--to=heiko@sntech.de \
--cc=ChrisXinchao@outlook.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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