From: "Dragan Simic" <dsimic@manjaro.org>
To: "Jun Yan" <jerrysteve1101@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, heiko@sntech.de,
alchark@gmail.com
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: Add OneThing Edge Cube series
Date: Sat, 31 Jan 2026 21:27:13 +0100 [thread overview]
Message-ID: <d2005c66-536c-8c0c-658a-fb6ed7b5f3c6@manjaro.org> (raw)
In-Reply-To: <20260131153106.31723-4-jerrysteve1101@gmail.com>
Hello Jun,
Please, see a quick remark below, for now.
On Saturday, January 31, 2026 16:31 CET, Jun Yan <jerrysteve1101@gmail.com> wrote:
> The OneThing Edge Cube (OEC) series features the RK3566 SoC, 8GB
> eMMC storage, and supports one SATA interface, one Gigabit Ethernet
> port, and one USB 3.0 port.
>
> Other than the difference in RAM capacity, the OEC and OEC-turbo are
> identical in all other specifications.
>
> Specification:
> - Rockchip RK3566
> - LPDDR4X 2GB (OEC) / 4GB (OEC-turbo)
> - eMMC 8GB
> - Gigabit Ethernet port x 1
> - USB 3.0 port x 1
> - USB-C 2.0 port x 1
> - 12V DC Power supply
> - SATA 3.0 connector x 1
>
> Signed-off-by: Jun Yan <jerrysteve1101@gmail.com>
> ---
> arch/arm64/boot/dts/rockchip/Makefile | 2 +
> .../rockchip/rk3566-onething-oec-turbo.dts | 10 +
> .../boot/dts/rockchip/rk3566-onething-oec.dts | 10 +
> .../dts/rockchip/rk3566-onething-oec.dtsi | 309 ++++++++++++++++++
> 4 files changed, 331 insertions(+)
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3566-onething-oec-turbo.dts
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3566-onething-oec.dts
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3566-onething-oec.dtsi
>
> diff --git a/arch/arm64/boot/dts/rockchip/Makefile b/arch/arm64/boot/dts/rockchip/Makefile
> index 4d384f153c13..ec57719e4573 100644
> --- a/arch/arm64/boot/dts/rockchip/Makefile
> +++ b/arch/arm64/boot/dts/rockchip/Makefile
> @@ -104,6 +104,8 @@ dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-anbernic-rg353v.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-anbernic-rg353vs.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-anbernic-rg503.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-odroid-m1s.dtb
> +dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-onething-oec.dtb
> +dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-onething-oec-turbo.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-orangepi-3b-v1.1.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-orangepi-3b-v2.1.dtb
> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3566-pinenote-v1.1.dtb
> diff --git a/arch/arm64/boot/dts/rockchip/rk3566-onething-oec-turbo.dts b/arch/arm64/boot/dts/rockchip/rk3566-onething-oec-turbo.dts
> new file mode 100644
> index 000000000000..16d0cd0cf577
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3566-onething-oec-turbo.dts
> @@ -0,0 +1,10 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +
> +/dts-v1/;
> +
> +#include "rk3566-onething-oec.dtsi"
> +
> +/ {
> + model = "OneThing OEC-turbo";
> + compatible = "onething,oec-turbo", "rockchip,rk3566";
> +};
> diff --git a/arch/arm64/boot/dts/rockchip/rk3566-onething-oec.dts b/arch/arm64/boot/dts/rockchip/rk3566-onething-oec.dts
> new file mode 100644
> index 000000000000..81da771ad63d
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3566-onething-oec.dts
> @@ -0,0 +1,10 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +
> +/dts-v1/;
> +
> +#include "rk3566-onething-oec.dtsi"
> +
> +/ {
> + model = "OneThing OEC";
> + compatible = "onething,oec", "rockchip,rk3566";
> +};
The only difference between the two OneThing OEC board variants is, as
far as I can tell, the amount of LPDDR4X DRAM they have, so I don't think
it's justified to have two separate board dts files that descend from the
common dtsi ancestor.
Having different amounts of DRAM on the same board design is present on
virtually all boards from other manufacturers, and some kind of special
DT treatment is needed only in some special cases, such as when different
types of DRAM are used for different capacities.
The different naming of the two board variants could be solved by having
something like this is the single board dts file:
model = "OneThing OEC/OEC-turbo";
Having two separate board dts files only makes it harder down the road,
such as having to build and provide two separate U-Boot builds, with no
real benefits. Every user can run free(1) to check the amount of available
DRAM on their board, which also tells them the board variant.
next prev parent reply other threads:[~2026-01-31 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 15:31 [PATCH v2 0/3] board: rockchip: add OneThing Edge Cube series Jun Yan
2026-01-31 15:31 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add Shenzhen OneThing Technologies Co., Ltd Jun Yan
2026-01-31 20:29 ` Conor Dooley
2026-01-31 15:31 ` [PATCH 2/3] dt-bindings: arm: rockchip: Add OneThing Edge Cube series Jun Yan
2026-01-31 20:29 ` Conor Dooley
2026-02-01 13:25 ` Jun Yan
2026-01-31 15:31 ` [PATCH 3/3] arm64: dts: " Jun Yan
2026-01-31 20:27 ` Dragan Simic [this message]
2026-02-01 13:14 ` Jun Yan
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=d2005c66-536c-8c0c-658a-fb6ed7b5f3c6@manjaro.org \
--to=dsimic@manjaro.org \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jerrysteve1101@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@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