From: Jun Yan <jerrysteve1101@gmail.com>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
heiko@sntech.de, alchark@gmail.com, dsimic@manjaro.org,
Jun Yan <jerrysteve1101@gmail.com>
Subject: [PATCH v2 0/3] board: rockchip: add OneThing Edge Cube series
Date: Sat, 31 Jan 2026 23:31:00 +0800 [thread overview]
Message-ID: <20260131153106.31723-1-jerrysteve1101@gmail.com> (raw)
This series adds support for the OneThing Edge Cube series, which were
initially marketed by OneThing Tech as PCDN (P2P Content Delivery Network)
devices. The Edge Cube series is based on Rockchip RK3566 SoC and is designed
for PCDN applications.
The V2 patches adds a new device, the OneThing OEC. Together with the V1 patch
OneThing OEC-turbo, these two devices share identical hardware specifications
except for the RAM capacity, enabling convenient support implementation.
The V1 patch was submitted quite some time ago and is now in an archived state[1].
it has not been processed due to scheduling conflicts – apologies for this.
Changes in v2:
- Fix typo in vendor-prefixes.
- Simplify company and device names.
- Add the new device OEC as part of the OneThing Edge Cube series for support.
- Set display-subsystem node to "disabled" instead of using "delete-node".
- Using generic node names for leds.
- Follow DTS codeing style in vcc5v0_usb_host_en pinctrl node.
- Modify the phy_mode of GMAC from rgmii to rgmii-id.
- Adjust device tree node ordering to follow code style.
Link to v1: https://lore.kernel.org/all/20250713163255.163669-1-jerrysteve1101@gmail.com/
[1] https://patchwork.kernel.org/project/linux-rockchip/cover/20250713163255.163669-1-jerrysteve1101@gmail.com/
Jun Yan (3):
dt-bindings: vendor-prefixes: Add Shenzhen OneThing Technologies Co.,
Ltd.
dt-bindings: arm: rockchip: Add OneThing Edge Cube series
arm64: dts: rockchip: Add OneThing Edge Cube series
.../devicetree/bindings/arm/rockchip.yaml | 6 +
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
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 | 313 ++++++++++++++++++
6 files changed, 343 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
--
2.52.0
next reply other threads:[~2026-01-31 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 15:31 Jun Yan [this message]
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
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=20260131153106.31723-1-jerrysteve1101@gmail.com \
--to=jerrysteve1101@gmail.com \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--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