From: Alex Bee <knaerzche@gmail.com>
To: Jonas Karlman <jonas@kwiboo.se>, Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Yao Zi <ziyao@disroot.org>, Chukun Pan <amadeus@jmu.edu.cn>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] arm64: dts: rockchip: Add ROCK 2A/2F, Sige1 and NanoPi Zero2
Date: Sun, 13 Jul 2025 21:13:44 +0200 [thread overview]
Message-ID: <702dc4bb-7b3c-4647-b84f-8516989b0836@gmail.com> (raw)
In-Reply-To: <20250712173805.584586-1-jonas@kwiboo.se>
Hi list, Hi Jonas,
> This series adds dt-bindings and initial device tree for the following
> Rockchip RK3528A boards:
> - Radxa ROCK 2A/2F
> - ArmSoM Sige1
> - FriendlyElec NanoPi Zero2
this only sub-related to this series: Is there any particular reason, why
we call the compatible "rockchip,rk3528" and not "rockchip,rk3528a"? From
what I can see all boards currently supported (and those in this series)
are having the RK3528A version of the SoC. I didn't follow the development
here, but there are differences - I did a quick compare of the datasheets
of those two SoC versions - it looks like RK3528 version has USB3-DRD
controller, while RK3528A has USB3 host-only controller. Also it seems to
have different video codec IPs and the DRAM controller additionally
supports LPDDR4X.
I guess it would be good to discuss this before this series is merged,
because re-naming *.dts files after they have been in a release is somewhat
impossible.
Regards,
Alex
>
> The bt/wifi_reg_on pins are described in the device tree using
> rfkill-gpio nodes.
>
> Changes in v3:
> - Rename led nodes to led-0/led-1
> - Remove pinctrl* props from sdio0
> - Collect a-b tags
>
> Changes in v2:
> - Limit sdmmc max-frequency to 100 MHz on ROCK 2A/2F
> - Drop clock-output-names prop from rtc node on Sige1 and NanoPi Zero2
> - Drop regulator-boot-on from usb 2.0 host regulators on Sige1
> - Add bluetooth and wifi nodes on Sige1
> - Collect t-b tag for NanoPi Zero2
>
> These boards can be booted from emmc or sd-card using the U-Boot 2025.07
> generic-rk3528 target or work-in-progress patches for these boards [1].
>
> For working bluetooth on ArmSoM Sige1 the patch "arm64: dts: rockchip:
> Fix UART DMA support for RK3528" [2] is required.
>
> [1] https://source.denx.de/u-boot/contributors/kwiboo/u-boot/-/commits/rk3528
> [2] https://lore.kernel.org/r/20250709210831.3170458-1-jonas@kwiboo.se
>
> Jonas Karlman (6):
> dt-bindings: arm: rockchip: Add Radxa ROCK 2A/2F
> arm64: dts: rockchip: Add Radxa ROCK 2A/2F
> dt-bindings: arm: rockchip: Add ArmSoM Sige1
> arm64: dts: rockchip: Add ArmSoM Sige1
> dt-bindings: arm: rockchip: Add FriendlyElec NanoPi Zero2
> arm64: dts: rockchip: Add FriendlyElec NanoPi Zero2
>
> .../devicetree/bindings/arm/rockchip.yaml | 17 +
> arch/arm64/boot/dts/rockchip/Makefile | 4 +
> .../boot/dts/rockchip/rk3528-armsom-sige1.dts | 465 ++++++++++++++++++
> .../boot/dts/rockchip/rk3528-nanopi-zero2.dts | 340 +++++++++++++
> .../boot/dts/rockchip/rk3528-rock-2.dtsi | 293 +++++++++++
> .../boot/dts/rockchip/rk3528-rock-2a.dts | 82 +++
> .../boot/dts/rockchip/rk3528-rock-2f.dts | 10 +
> 7 files changed, 1211 insertions(+)
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3528-armsom-sige1.dts
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3528-nanopi-zero2.dts
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3528-rock-2.dtsi
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3528-rock-2a.dts
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3528-rock-2f.dts
>
next prev parent reply other threads:[~2025-07-13 19:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-12 17:37 Jonas Karlman
2025-07-12 17:37 ` [PATCH v3 1/6] dt-bindings: arm: rockchip: Add Radxa ROCK 2A/2F Jonas Karlman
2025-07-12 17:37 ` [PATCH v3 2/6] arm64: dts: " Jonas Karlman
2025-07-13 13:39 ` Yao Zi
2025-07-14 9:44 ` Nicolas Frattaroli
2025-07-14 10:49 ` Jonas Karlman
2025-07-14 11:15 ` Nicolas Frattaroli
2025-07-12 17:37 ` [PATCH v3 3/6] dt-bindings: arm: rockchip: Add ArmSoM Sige1 Jonas Karlman
2025-07-12 17:37 ` [PATCH v3 4/6] arm64: dts: " Jonas Karlman
2025-07-15 14:01 ` Chukun Pan
2025-07-15 14:21 ` Jonas Karlman
2025-07-16 7:00 ` Chukun Pan
2025-07-12 17:37 ` [PATCH v3 5/6] dt-bindings: arm: rockchip: Add FriendlyElec NanoPi Zero2 Jonas Karlman
2025-07-12 17:37 ` [PATCH v3 6/6] arm64: dts: " Jonas Karlman
2025-07-13 19:13 ` Alex Bee [this message]
2025-07-13 20:13 ` [PATCH v3 0/6] arm64: dts: rockchip: Add ROCK 2A/2F, Sige1 and " Jonas Karlman
2025-07-13 20:56 ` Alex Bee
2025-07-14 0:04 ` Jonas Karlman
2025-07-14 5:53 ` Alex Bee
2025-07-15 18:56 ` Heiko Stübner
2025-07-19 9:58 ` Alex Bee
2025-07-19 14:30 ` Chukun Pan
2025-07-19 16:07 ` Alex Bee
2025-07-20 9:45 ` Alex Bee
2025-07-20 13:40 ` Chukun Pan
2025-07-20 15:51 ` Alex Bee
2025-07-21 14:00 ` Chukun Pan
2025-07-21 18:07 ` Alex Bee
2025-07-23 13:40 ` Chukun Pan
2025-07-26 11:07 ` Alex Bee
2025-07-14 1:00 ` Yao Zi
2025-07-14 8:52 ` Nicolas Frattaroli
2025-07-14 15:24 ` 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=702dc4bb-7b3c-4647-b84f-8516989b0836@gmail.com \
--to=knaerzche@gmail.com \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=ziyao@disroot.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
all inboxes | Powered by JetHome®