From: Jianfeng Liu <liujianfeng1994@gmail.com>
To: peter.chen@cixtech.com
Cc: arnd@arndb.de, catalin.marinas@arm.com,
cix-kernel-upstream@cixtech.com, conor+dt@kernel.org,
devicetree@vger.kernel.org, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, marcin@juszkiewicz.com.pl,
robh@kernel.org, will@kernel.org
Subject: Re: [PATCH v2 0/6] arm64: Introduce CIX P1 (SKY1) SoC
Date: Thu, 27 Feb 2025 12:52:36 +0800 [thread overview]
Message-ID: <20250227045236.2830419-1-liujianfeng1994@gmail.com> (raw)
In-Reply-To: <20250226012136.854614-1-peter.chen@cixtech.com>
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
next prev parent reply other threads:[~2025-02-27 4:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 1:21 [PATCH v2 0/6] arm64: Introduce CIX P1 (SKY1) SoC Peter Chen
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 ` Jianfeng Liu [this message]
2025-02-27 8:02 ` [PATCH v2 0/6] arm64: Introduce CIX P1 (SKY1) SoC 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=20250227045236.2830419-1-liujianfeng1994@gmail.com \
--to=liujianfeng1994@gmail.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=peter.chen@cixtech.com \
--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