From: Hongyang Zhao <hongyang.zhao@thundersoft.com>
To: linux-arm-msm@vger.kernel.org
Cc: casey.connolly@linaro.org, christopher.obbard@linaro.org,
loic.minier@oss.qualcomm.com, andersson@kernel.org,
Hongyang Zhao <hongyang.zhao@thundersoft.com>
Subject: [PATCH v5 0/2] arm64: dts: qcom: rubikpi3: Add qcs6490-rubikpi3 board dts
Date: Sat, 25 Oct 2025 20:27:21 +0800 [thread overview]
Message-ID: <20251025122724.633766-1-hongyang.zhao@thundersoft.com> (raw)
RUBIK Pi 3 (https://rubikpi.ai/), a lightweight development board based on
Qualcomm Dragonwing™ QCS6490 platform, is the first Pi built on Qualcomm
AI platforms for developers.
This commit enables the following features:
Works:
- Bluetooth (AP6256)
- Wi-Fi (AP6256)
- Ethernet (AX88179B connected to UPD720201)
- FAN
- Two USB Type-A 3.0 ports (UPD720201 connected to PCIe0)
- M.2 M-Key 2280 PCIe 3.0
- RTC
- USB Type-C
- USB Type-A 2.0 port
- 40PIN: I2C x1, UART x1
---
Changes in v5:
- Fix device tree formatting issues.
- Add fan control that follows CPU0 temperature.
- Link to v4: https://lore.kernel.org/linux-arm-msm/20250930043258.249641-1-hongyang.zhao@thundersoft.com/
Changes in v4:
- Enable PCIe0 node.
- Added AX88179B Ethernet and UPD720201 USBHUB power control.
- Delete the nodes and attributes defined in sc7280.dtsi.
- Modify qcom.yaml to add binding for the Thundercomm RUBIK Pi 3 board.
- Link to v3: https://lore.kernel.org/linux-arm-msm/20250924161120.27051-1-hongyang.zhao@thundersoft.com/
Changes in v3:
- Rebase on linux-next/master.
- Link to v2: https://lore.kernel.org/linux-arm-msm/20250924121541.128582-1-hongyang.zhao@thundersoft.com/
Changes in v2:
- Fix problems found when running device tree check.
- Enable USB2.0 interface.
- Link to v1: https://lore.kernel.org/linux-arm-msm/20250923064330.518784-1-hongyang.zhao@thundersoft.com/
---
Hongyang Zhao (2):
arm64: dts: qcom: rubikpi3: Add qcs6490-rubikpi3 board dts
dt-bindings: arm: qcom: rubikpi3: document rubikpi3 board binding
.../devicetree/bindings/arm/qcom.yaml | 1 +
arch/arm64/boot/dts/qcom/Makefile | 1 +
.../dts/qcom/qcs6490-thundercomm-rubikpi3.dts | 1390 +++++++++++++++++
3 files changed, 1392 insertions(+)
create mode 100644 arch/arm64/boot/dts/qcom/qcs6490-thundercomm-rubikpi3.dts
base-commit: 72fb0170ef1f45addf726319c52a0562b6913707
--
2.43.0
next reply other threads:[~2025-10-25 12:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 12:27 Hongyang Zhao [this message]
2025-10-25 12:27 ` [PATCH v5 1/2] arm64: dts: qcom: rubikpi3: Add qcs6490-rubikpi3 board dts Hongyang Zhao
2025-10-27 14:51 ` Dmitry Baryshkov
2025-10-31 9:27 ` Hongyang Zhao
2025-11-01 8:37 ` Dmitry Baryshkov
2025-11-02 3:09 ` Hongyang Zhao
2025-11-02 22:13 ` Dmitry Baryshkov
2025-11-03 4:20 ` Hongyang Zhao
2025-11-03 11:57 ` Konrad Dybcio
2025-11-03 12:33 ` Hongyang Zhao
2025-11-03 12:53 ` Konrad Dybcio
2025-10-25 12:27 ` [PATCH v5 2/2] dt-bindings: arm: qcom: rubikpi3: document rubikpi3 board binding Hongyang Zhao
2025-10-26 9:05 ` Krzysztof Kozlowski
2025-10-30 2:33 ` [PATCH v5 2/2] arm64: dts: qcom: rubikpi3: Add qcs6490-rubikpi3 board dts Hongyang Zhao
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=20251025122724.633766-1-hongyang.zhao@thundersoft.com \
--to=hongyang.zhao@thundersoft.com \
--cc=andersson@kernel.org \
--cc=casey.connolly@linaro.org \
--cc=christopher.obbard@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=loic.minier@oss.qualcomm.com \
/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;
as well as URLs for NNTP newsgroup(s).