arm64: Introduce CIX P1 (SKY1) SoC
Subsystems (4)
v2 cover arm64: Introduce CIX P1 (SKY1) SoC
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
Signature · 1 line
2.25.1
PATCH v2 1/6 dt-bindings: vendor-prefixes: Add CIX Technology Group Co., Ltd.
CIX Technology Group Co., Ltd. is a high performance Arm SoC design company. Link: https://www.cixtech.com/.
--- Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++ 1 file changed, 2 insertions(+)
Documentation/devicetree/bindings/vendor-prefixes.yaml +2 -0
@@ -302,6 +302,8 @@ patternProperties: description: Cirrus Logic, Inc. "^cisco,.*": description: Cisco Systems, Inc. + "^cix,.*": + description: CIX Technology Group Co., Ltd. "^clockwork,.*": description: Clockwork Tech LLC "^cloos,.*":
Signature · 1 line
2.25.1
Krzysztof Kozlowski
maintainerRe: [PATCH v2 1/6] dt-bindings: vendor-prefixes: Add CIX Technology Group Co., Ltd.
Quoted 5 lines · Peter Chen
CIX Technology Group Co., Ltd. is a high performance Arm SoC design company. Link: https://www.cixtech.com/.
Acked-by Fugang Duan <[email protected]>Signed-off-by Peter Chen <[email protected]>
I would give an Ack here, but if it is going to be ignored feels like not useful. :/
Best regards,
Krzysztof
Re: [PATCH v2 1/6] dt-bindings: vendor-prefixes: Add CIX Technology Group Co., Ltd.
In reply to Peter ChenQuoted 5 lines · Peter Chen
CIX Technology Group Co., Ltd. is a high performance Arm SoC design company. Link: https://www.cixtech.com/.
Acked-by Fugang Duan <[email protected]>Signed-off-by Peter Chen <[email protected]>
---
<form letter>
This is an automated instruction, just in case, because many review tags are being ignored. If you know the process, you can skip it (please do not feel offended by me posting it here - no bad intentions intended). If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions of patchset, under or above your Signed-off-by tag, unless patch changed significantly (e.g. new properties added to the DT bindings). Tag is "received", when provided in a message replied to you on the mailing list. Tools like b4 can help here. However, there's no need to repost patches *only* to add the tags. The upstream maintainer will do that for tags received on the version they apply.
Full context and explanation:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
</form letter>
Best regards,
Krzysztof
PATCH v2 2/6 dt-bindings: arm: add CIX P1 (SKY1) SoC
In reply to Peter ChenAdd device tree bindings for CIX P1 (Internal name sky1) Arm SoC, it consists several SoC models like CP8180, CD8180, etc.
--- .../devicetree/bindings/arm/cix.yaml | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/cix.yaml
Documentation/devicetree/bindings/arm/cix.yaml new file +26 -0
@@ -0,0 +1,26 @@ +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/arm/cix.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: CIX platforms + +maintainers: + - Peter Chen <[email protected]> + - Fugang Duan <[email protected]> + +properties: + $nodename: + const: '/' + compatible: + oneOf: + + - description: Radxa Orion O6 + items: + - const: radxa,orion-o6 + - const: cix,sky1 + +additionalProperties: true + +...
Signature · 1 line
2.25.1
Krzysztof Kozlowski
maintainerRe: [PATCH v2 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC
Quoted 6 lines · Peter Chen
Add device tree bindings for CIX P1 (Internal name sky1) Arm SoC, it consists several SoC models like CP8180, CD8180, etc.
Acked-by Fugang Duan <[email protected]>Signed-off-by Peter Chen <[email protected]>---
<form letter>
This is a friendly reminder during the review process.
It looks like you received a tag and forgot to add it.
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions of patchset, under or above your Signed-off-by tag, unless patch changed significantly (e.g. new properties added to the DT bindings). Tag is "received", when provided in a message replied to you on the mailing list. Tools like b4 can help here. However, there's no need to repost patches *only* to add the tags. The upstream maintainer will do that for tags received on the version they apply.
Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
If a tag was not added on purpose, please state why and what changed. </form letter>
Best regards,
Krzysztof
Re: [PATCH v2 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC
Quoted 24 lines · Krzysztof Kozlowski
EXTERNAL EMAIL
Quoted 6 lines · Peter Chen
Add device tree bindings for CIX P1 (Internal name sky1) Arm SoC, it consists several SoC models like CP8180, CD8180, etc.
Acked-by Fugang Duan <[email protected]>Signed-off-by Peter Chen <[email protected]>---
<form letter>
This is a friendly reminder during the review process.It looks like you received a tag and forgot to add it.
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions of patchset, under or above your Signed-off-by tag, unless patch changed significantly (e.g. new properties added to the DT bindings). Tag is "received", when provided in a message replied to you on the mailing list. Tools like b4 can help here. However, there's no need to repost patches *only* to add the tags. The upstream maintainer will do that for tags received on the version they apply.
Quoted 6 lines
Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577If a tag was not added on purpose, please state why and what changed. </form letter>
I have checked the review-process again at:
https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=935897
It seems no one gives any Reviewed-by or Acked-by Tag.
If I am missing something, please correct me.
Signature · 2 lines
Best regards, Peter
Krzysztof Kozlowski
maintainerRe: [PATCH v2 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC
Quoted 28 lines · Peter Chen
Quoted 27 lines · Krzysztof Kozlowski
EXTERNAL EMAIL
Quoted 6 lines · Peter Chen
Add device tree bindings for CIX P1 (Internal name sky1) Arm SoC, it consists several SoC models like CP8180, CD8180, etc.
Acked-by Fugang Duan <[email protected]>Signed-off-by Peter Chen <[email protected]>---
<form letter>
This is a friendly reminder during the review process.It looks like you received a tag and forgot to add it.
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions of patchset, under or above your Signed-off-by tag, unless patch changed significantly (e.g. new properties added to the DT bindings). Tag is "received", when provided in a message replied to you on the mailing list. Tools like b4 can help here. However, there's no need to repost patches *only* to add the tags. The upstream maintainer will do that for tags received on the version they apply.Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
Quoted 6 lines
Quoted 3 lines
If a tag was not added on purpose, please state why and what changed. </form letter>
I have checked the review-process again at:
https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=935897
This does not matter - that's not a patchwork anyone uses...
Quoted 1 line
It seems no one gives any Reviewed-by or Acked-by Tag.
You were directly addressed! So you got email and what did you do with it?
And lists received it:
https://lore.kernel.org/all/[email protected]/
Quoted 3 lines
If I am missing something, please correct me.
Best regards,
Krzysztof
Re: [PATCH v2 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC
Quoted 33 lines · Krzysztof Kozlowski
Quoted 26 lines
Quoted 26 lines · Peter Chen
Quoted 6 lines
Add device tree bindings for CIX P1 (Internal name sky1) Arm SoC, it consists several SoC models like CP8180, CD8180, etc.
Acked-by Fugang Duan <[email protected]>Signed-off-by Peter Chen <[email protected]>---
<form letter>
This is a friendly reminder during the review process.It looks like you received a tag and forgot to add it.
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions of patchset, under or above your Signed-off-by tag, unless patch changed significantly (e.g. new properties added to the DT bindings). Tag is "received", when provided in a message replied to you on the mailing list. Tools like b4 can help here. However, there's no need to repost patches *only* to add the tags. The upstream maintainer will do that for tags received on the version they apply.Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577Quoted 6 lines
Quoted 3 lines
If a tag was not added on purpose, please state why and what changed. </form letter>
I have checked the review-process again at:
https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=935897
Quoted 9 lines
This does not matter - that's not a patchwork anyone uses...
Quoted 1 line
It seems no one gives any Reviewed-by or Acked-by Tag.
You were directly addressed! So you got email and what did you do with it?
And lists received it:
https://lore.kernel.org/all/[email protected]/
I am sorry about that. I checked this email with our IT engineers at office365 administration page, it was not received by Microsoft office365 server, we don't know what's the reason.
I will put your Reviewed-by tag when sending v3 patch, may I get your Ack for the 1st patch:
https://lore.kernel.org/linux-arm-kernel/[email protected]/T/#u
Signature · 2 lines
Best regards, Peter
Krzysztof Kozlowski
maintainerRe: [PATCH v2 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC
Quoted 40 lines · Peter Chen
Quoted 39 lines · Krzysztof Kozlowski
Quoted 26 lines
Quoted 26 lines · Peter Chen
Quoted 6 lines
Add device tree bindings for CIX P1 (Internal name sky1) Arm SoC, it consists several SoC models like CP8180, CD8180, etc.
Acked-by Fugang Duan <[email protected]>Signed-off-by Peter Chen <[email protected]>---
<form letter>
This is a friendly reminder during the review process.It looks like you received a tag and forgot to add it.
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions of patchset, under or above your Signed-off-by tag, unless patch changed significantly (e.g. new properties added to the DT bindings). Tag is "received", when provided in a message replied to you on the mailing list. Tools like b4 can help here. However, there's no need to repost patches *only* to add the tags. The upstream maintainer will do that for tags received on the version they apply.Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577Quoted 6 lines
Quoted 3 lines
If a tag was not added on purpose, please state why and what changed. </form letter>
I have checked the review-process again at:
https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=935897This does not matter - that's not a patchwork anyone uses...
Quoted 1 line
It seems no one gives any Reviewed-by or Acked-by Tag.
You were directly addressed! So you got email and what did you do with it?
Quoted 7 lines
Quoted 3 lines
And lists received it:
https://lore.kernel.org/all/[email protected]/I am sorry about that. I checked this email with our IT engineers at office365 administration page, it was not received by Microsoft office365 server, we don't know what's the reason.
That's the only email which did not reach you, I think. 4 or 5 others did, so this could mean your system will spam/reject silently anything with review tag (or email address).
If so, your corporate mail system is not suitable for upstream work (Microsoft outlook is known of poor quality in that matter and that's not the first case people have trouble with Outlook servers) and maybe you should switch to b4-relay and other mail boxes.
Quoted 4 lines
I will put your Reviewed-by tag when sending v3 patch, may I get your Ack for the 1st patch:
https://lore.kernel.org/linux-arm-kernel/[email protected]/T/#u
I'll send it, but I still have doubts Microsoft won't put me in spam :/
Best regards,
Krzysztof
Re: [PATCH v2 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC
Quoted 29 lines · Krzysztof Kozlowski
Quoted 10 lines
Quoted 10 lines
Quoted 3 lines
I have checked the review-process again at:
https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=935897This does not matter - that's not a patchwork anyone uses...
Quoted 1 line
It seems no one gives any Reviewed-by or Acked-by Tag.
You were directly addressed! So you got email and what did you do with it?
Quoted 7 lines
Quoted 3 lines
And lists received it:
https://lore.kernel.org/all/[email protected]/I am sorry about that. I checked this email with our IT engineers at office365 administration page, it was not received by Microsoft office365 server, we don't know what's the reason.
That's the only email which did not reach you, I think. 4 or 5 others did, so this could mean your system will spam/reject silently anything with review tag (or email address).
If so, your corporate mail system is not suitable for upstream work (Microsoft outlook is known of poor quality in that matter and that's not the first case people have trouble with Outlook servers) and maybe you should switch to b4-relay and other mail boxes.
Quoted 1 line
Quoted 7 lines
Quoted 3 lines
I will put your Reviewed-by tag when sending v3 patch, may I get your Ack for the 1st patch:
https://lore.kernel.org/linux-arm-kernel/[email protected]/T/#uI'll send it, but I still have doubts Microsoft won't put me in spam :/
Hi Krzysztof,
Do you use kernel.org as your smtp server? It may kernel.org's smtp server issue, both lore.kernel.org[1] and patchwork.kernel.org[2] have received your ack for my v2 patch.
But only lore.kernel.org [3] received your reviewed-by Tag for my v1 patch, the patch.kernel.org[4] did not receive it, office365 server for my company also did not receive it.
Another strange is I did not received [5], but my colleagues in our upstream mail list ([email protected]) received it, I have not in that list at that time (now I am at it), but my name is at your reply to, it seems kernel.org did not send to me.
That's just my suspect, if someone meets the similar issues in future, it may prove my suspect.
[1] https://lore.kernel.org/linux-arm-kernel/[email protected]/
[2] https://patchwork.kernel.org/project/linux-arm-kernel/patch/[email protected]/#26265571
[3] https://lore.kernel.org/all/[email protected]/
[4] https://patchwork.kernel.org/project/linux-arm-kernel/patch/[email protected]/
[5] https://lore.kernel.org/all/[email protected]/
Signature · 2 lines
Best regards, Peter
PATCH v2 3/6 MAINTAINERS: Add CIX SoC maintainer entry
In reply to Peter ChenUsing this entry as the maintainers information for CIX SKY series SoCs.
--- MAINTAINERS | 8 ++++++++ 1 file changed, 8 insertions(+)
MAINTAINERS +8 -0
@@ -2354,6 +2354,14 @@ F: arch/arm/boot/compressed/misc-ep93xx.h F: arch/arm/mach-ep93xx/ F: drivers/iio/adc/ep93xx_adc.c +ARM/CIX SKY ARM ARCHITECTURE +M: Peter Chen <[email protected]> +M: Fugang Duan <[email protected]> +R: CIX Linux Kernel Upstream Group <[email protected]> +L: [email protected] (moderated for non-subscribers) +S: Maintained +F: Documentation/devicetree/bindings/arm/cix.yaml + ARM/CLKDEV SUPPORT M: Russell King <[email protected]> L: [email protected] (moderated for non-subscribers)
Signature · 1 line
2.25.1
PATCH v2 4/6 arm64: Kconfig: add ARCH_CIX for cix silicons
In reply to Peter ChenFrom: Fugang Duan <[email protected]>
Add ARCH_CIX for CIX SoC series support.
---
Changes for v2:
- Ordered Kconfig config entry by alpha-numerically
arch/arm64/Kconfig.platforms | 6 ++++++ 1 file changed, 6 insertions(+)
arch/arm64/Kconfig.platforms +6 -0
@@ -106,6 +106,12 @@ config ARCH_BLAIZE help This enables support for the Blaize SoC family +config ARCH_CIX + bool "Cixtech SoC family" + help + This enables support for the Cixtech SoC family, + like P1(sky1). + config ARCH_EXYNOS bool "Samsung Exynos SoC family" select COMMON_CLK_SAMSUNG
Signature · 1 line
2.25.1
PATCH v2 5/6 arm64: defconfig: Enable CIX SoC
In reply to Peter ChenEnable CIX SoC support at ARM64 defconfig
---
Changes for v2:
- Corrects the Ack tag's name
arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+)
arch/arm64/configs/defconfig +1 -0
@@ -45,6 +45,7 @@ CONFIG_ARCH_BCMBCA=y CONFIG_ARCH_BRCMSTB=y CONFIG_ARCH_BERLIN=y CONFIG_ARCH_BLAIZE=y +CONFIG_ARCH_CIX=y CONFIG_ARCH_EXYNOS=y CONFIG_ARCH_SPARX5=y CONFIG_ARCH_K3=y
Signature · 1 line
2.25.1
PATCH v2 6/6 arm64: dts: cix: add initial CIX P1(SKY1) dts support
In reply to Peter ChenCIX SKY1 SoC is high performance Armv9 SoC designed by Cixtech, and Orion O6 is open source motherboard launched by Radxa. See below for detail:
https://docs.radxa.com/en/orion/o6/getting-started/introduction
In this commit, it only adds limited components for running initramfs at Orion O6.
---
Changes for v2:
- Corrects the SoF tag's name
- Fix several coding sytle issues
- move linux,cma node to dts file
- delete memory node, memory size is passed by firmware
- delete uart2 node which will be added in future patches
- Improve for pmu and cpu node to stands for more specific cpu model
- Improve the timer node and add hypervisor virtual timer irq
- Pass "make O=$OUTKNL CHECK_DTBS=y W=1 cix/sky1-orion-o6.dtb"
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 ++++++++++++++++++++++ 4 files changed, 246 insertions(+) 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
arch/arm64/boot/dts/Makefile +1 -0
@@ -13,6 +13,7 @@ subdir-y += bitmain subdir-y += blaize subdir-y += broadcom subdir-y += cavium +subdir-y += cix subdir-y += exynos subdir-y += freescale subdir-y += hisilicon
arch/arm64/boot/dts/cix/Makefile new file +2 -0
@@ -0,0 +1,2 @@ +# SPDX-License-Identifier: GPL-2.0 +dtb-$(CONFIG_ARCH_CIX) += sky1-orion-o6.dtb
arch/arm64/boot/dts/cix/sky1-orion-o6.dts new file +26 -0
@@ -0,0 +1,26 @@ +// SPDX-License-Identifier: BSD-3-Clause +/* + * Copyright 2025 Cix Technology Group Co., Ltd. + * + */ + +/dts-v1/; + +#include "sky1.dtsi" +/ { + model = "Radxa Orion O6"; + compatible = "radxa,orion-o6", "cix,sky1"; + + reserved-memory { + #address-cells = <2>; + #size-cells = <2>; + ranges; + + linux,cma { + compatible = "shared-dma-pool"; + reusable; + size = <0x0 0x28000000>; + linux,cma-default; + }; + }; +};
arch/arm64/boot/dts/cix/sky1.dtsi new file +217 -0
217 lines not on this page · raw message
Signature · 1 line
2.25.1
Krzysztof Kozlowski
maintainerRe: [PATCH v2 6/6] arm64: dts: cix: add initial CIX P1(SKY1) dts support
Quoted 8 lines · Peter Chen
arch/arm64/boot/dts/cix/sky1.dtsi new file +8
-0+ core7 { + cpu = <&cpu7>; + }; + core8 { + cpu = <&cpu8>; + }; + core9 { + cpu = <&cpu9>;
arch/arm64/boot/dts/cix/sky1.dtsi line 154
Quoted 10 lines
arch/arm64/boot/dts/cix/sky1.dtsi new file +10
-0+ }; + core10 { + cpu = <&cpu10>; + }; + core11 { + cpu = <&cpu11>; + }; + }; + }; +
Stray blank line
Quoted 17 lines
arch/arm64/boot/dts/cix/sky1.dtsi new file +17
-0+ }; + + pmu-a520 { + compatible = "arm,cortex-a520-pmu"; + interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_LOW>; + }; + + pmu-a720 { + compatible = "arm,cortex-a720-pmu"; + interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_LOW>; + }; + + pmu-spe { + compatible = "arm,statistical-profiling-extension-v1"; + interrupts = <GIC_PPI 5 IRQ_TYPE_LEVEL_LOW>; + }; +
arch/arm64/boot/dts/cix/sky1.dtsi line 181
Quoted 10 lines
arch/arm64/boot/dts/cix/sky1.dtsi new file +10
-0+ psci { + compatible = "arm,psci-1.0"; + method = "smc"; + }; + + soc@0 { + compatible = "simple-bus"; + #address-cells = <2>; + #size-cells = <2>; + ranges = <0 0 0 0 0x20 0>;
Ranges is like reg, so after compatible. See DTS coding style.
Best regards,
Krzysztof
Hi Peter,
I'm really happy to see the linux mainline upstream work sent. And I have also reveived radxa orion o6 before the Chinese new year. I have heard that CIX is testing vendor kernel with ACPI. And now the mainline upstream work is based on devicetree. I want to know what the upstream work of CIX would go in the future, are we going to toggle to ACPI instead of devicetree?
And it would be good to let outsiders know the plan/roadmap of upstream. For example collaboara is doing good job on upstreaming rockchip[1][2] and mediatek[3] socs.
[1] https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md
[2] https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3576/-/blob/main/mainline-status.md?ref_type=heads
[3] https://gitlab.collabora.com/mediatek/aiot/wiki/-/blob/main/mainline-status.md
Best regards,
Jianfeng
Quoted 9 lines · Jianfeng Liu
Hi Peter,
I'm really happy to see the linux mainline upstream work sent. And I have also reveived radxa orion o6 before the Chinese new year. I have heard that CIX is testing vendor kernel with ACPI. And now the mainline upstream work is based on devicetree. I want to know what the upstream work of CIX would go in the future, are we going to toggle to ACPI instead of devicetree?
Quoted 8 lines
And it would be good to let outsiders know the plan/roadmap of upstream. For example collaboara is doing good job on upstreaming rockchip[1][2] and mediatek[3] socs.
[1] https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md
[2] https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3576/-/blob/main/mainline-status.md?ref_type=heads
[3] https://gitlab.collabora.com/mediatek/aiot/wiki/-/blob/main/mainline-status.md
Hi Jianfeng,
Thanks for your interesting of our hardware. Radxa will open our v6.1 device tree vendor kernel source code at the beginning of next month. For ACPI vendor kernel source code based on v6.6, it has planned to open at Q2 of this year.
For upstream, we will submit support based on device tree first, since some common code changes are needed for supporting ACPI well at Arm, it may involve lots of discussion. After most of IP drivers are supported by upstream kernel, we will start ACPI upstream work.
For upstream status record for CIX SoC, we will find some public place for it.
Signature · 2 lines
Best regards, Peter