From: Jun Yan <jerrysteve1101@gmail.com>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
wens@kernel.org, jernej.skrabec@gmail.com, samuel@sholland.org,
mripard@kernel.org, Jun Yan <jerrysteve1101@gmail.com>
Subject: [PATCH v2 0/3] board: sunxi: Add TaiqiCat (TQC) A01
Date: Fri, 27 Feb 2026 23:57:57 +0800 [thread overview]
Message-ID: <20260227155801.211376-1-jerrysteve1101@gmail.com> (raw)
This series adds support for the TaiqiCat (TQC) A01 —
a set-top box based on the Allwinner H6 SoC.
Originally released by Ultrapower(UQSoft) as a blockchain terminal,
the device has been discontinued and is no longer officially
supported.
https://web.archive.org/web/20190409213228/https://tq.ultrapower.com.cn/product.html
Jun Yan (3):
dt-bindings: vendor-prefixes: Add Beijing Ultrapower Software Co.,
Ltd.
dt-bindings: arm: sunxi: Add TaiqiCat (TQC) A01
arm64: dts: allwinner: h6: Add TaiqiCat (TQC) A01 support
.../devicetree/bindings/arm/sunxi.yaml | 5 +
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
arch/arm64/boot/dts/allwinner/Makefile | 1 +
.../dts/allwinner/sun50i-h6-taiqicat-a01.dts | 361 ++++++++++++++++++
4 files changed, 369 insertions(+)
create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h6-taiqicat-a01.dts
--
2.53.0
next reply other threads:[~2026-02-27 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 15:57 Jun Yan [this message]
2026-02-27 15:57 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add Beijing Ultrapower Software Co., Ltd Jun Yan
2026-02-28 10:51 ` Krzysztof Kozlowski
2026-02-27 15:57 ` [PATCH v2 2/3] dt-bindings: arm: sunxi: Add TaiqiCat (TQC) A01 Jun Yan
2026-02-28 10:51 ` Krzysztof Kozlowski
2026-02-27 15:58 ` [PATCH v2 3/3] arm64: dts: allwinner: h6: Add TaiqiCat (TQC) A01 support Jun Yan
2026-03-01 21:54 ` Andre Przywara
2026-03-02 1:48 ` Jun Yan
2026-02-28 1:47 ` [PATCH v2 0/3] board: sunxi: Add TaiqiCat (TQC) A01 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=20260227155801.211376-1-jerrysteve1101@gmail.com \
--to=jerrysteve1101@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@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