From: Peter Chen <peter.chen@cixtech.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
catalin.marinas@arm.com, will@kernel.org, arnd@arndb.de
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, cix-kernel-upstream@cixtech.com,
marcin@juszkiewicz.com.pl, Peter Chen <peter.chen@cixtech.com>
Subject: [PATCH v2 0/6] arm64: Introduce CIX P1 (SKY1) SoC
Date: Wed, 26 Feb 2025 09:21:30 +0800 [thread overview]
Message-ID: <20250226012136.854614-1-peter.chen@cixtech.com> (raw)
Cixtech P1 (internal name sky1) is high performance generic Armv9 SoC.
Orion O6 is the world's first open source Arm V9 Motherboard built by
Radxa. You could find brief introduction for SoC and related boards at:
https://radxa.com/products/orion/o6#overview
In this series, we add initial SoC and board support for Kernel building.
Patch 1-2: Add dt-binding doc for CIX and its sky1 SoC
Patch 3: add related maintainter entry
Patch 4-5: add Arm64 build support
Patch 6: add initial dts support for SoC and Orion O6 board
To run upstream kernel at Orion O6 board, you need to use BIOS
released by Radxa:
https://docs.radxa.com/en/orion/o6/bios/install-bios
Changes for v2:
- Pass dts build check with below commands:
make O=$OUTKNL dt_binding_check DT_SCHEMA_FILES=vendor-prefixes.yaml
make O=$OUTKNL dt_binding_check DT_SCHEMA_FILES=arm/cix.yaml
make O=$OUTKNL CHECK_DTBS=y W=1 cix/sky1-orion-o6.dtb
- Re-order the patch set, and move vendor-perfixes to the 1st patch.
- Patch 4: Ordered Kconfig config entry by alpha-numerically
- Patch 5: Corrects the Ack tag's name
- Patch 6: see below.
1) Corrects the SoF tag's name
2) Fix several coding sytle issues
3) move linux,cma node to dts file
4) delete memory node, memory size is passed by firmware
5) delete uart2 node which will be added in future patches
6) Improve for pmu and cpu node to stands for more specific cpu model
7) Improve the timer node and add hypervisor virtual timer irq
Fugang Duan (1):
arm64: Kconfig: add ARCH_CIX for cix silicons
Peter Chen (5):
dt-bindings: vendor-prefixes: Add CIX Technology Group Co., Ltd.
dt-bindings: arm: add CIX P1 (SKY1) SoC
MAINTAINERS: Add CIX SoC maintainer entry
arm64: defconfig: Enable CIX SoC
arm64: dts: cix: add initial CIX P1(SKY1) dts support
.../devicetree/bindings/arm/cix.yaml | 26 +++
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
MAINTAINERS | 8 +
arch/arm64/Kconfig.platforms | 6 +
arch/arm64/boot/dts/Makefile | 1 +
arch/arm64/boot/dts/cix/Makefile | 2 +
arch/arm64/boot/dts/cix/sky1-orion-o6.dts | 26 +++
arch/arm64/boot/dts/cix/sky1.dtsi | 217 ++++++++++++++++++
arch/arm64/configs/defconfig | 1 +
9 files changed, 289 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/cix.yaml
create mode 100644 arch/arm64/boot/dts/cix/Makefile
create mode 100644 arch/arm64/boot/dts/cix/sky1-orion-o6.dts
create mode 100644 arch/arm64/boot/dts/cix/sky1.dtsi
--
2.25.1
next reply other threads:[~2025-02-26 1:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 1:21 Peter Chen [this message]
2025-02-26 1:21 ` [PATCH v2 1/6] dt-bindings: vendor-prefixes: Add CIX Technology Group Co., Ltd Peter Chen
2025-02-26 7:02 ` Krzysztof Kozlowski
2025-02-26 10:31 ` Krzysztof Kozlowski
2025-02-26 1:21 ` [PATCH v2 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC Peter Chen
2025-02-26 7:02 ` Krzysztof Kozlowski
2025-02-26 8:09 ` Peter Chen
2025-02-26 8:40 ` Krzysztof Kozlowski
2025-02-26 10:26 ` Peter Chen
2025-02-26 10:30 ` Krzysztof Kozlowski
2025-02-26 12:59 ` Peter Chen
2025-02-26 1:21 ` [PATCH v2 3/6] MAINTAINERS: Add CIX SoC maintainer entry Peter Chen
2025-02-26 1:21 ` [PATCH v2 4/6] arm64: Kconfig: add ARCH_CIX for cix silicons Peter Chen
2025-02-26 1:21 ` [PATCH v2 5/6] arm64: defconfig: Enable CIX SoC Peter Chen
2025-02-26 1:21 ` [PATCH v2 6/6] arm64: dts: cix: add initial CIX P1(SKY1) dts support Peter Chen
2025-02-26 7:05 ` Krzysztof Kozlowski
2025-02-27 4:52 ` [PATCH v2 0/6] arm64: Introduce CIX P1 (SKY1) SoC Jianfeng Liu
2025-02-27 8:02 ` Peter Chen
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=20250226012136.854614-1-peter.chen@cixtech.com \
--to=peter.chen@cixtech.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin@juszkiewicz.com.pl \
--cc=robh@kernel.org \
--cc=will@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