linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@cixtech.com>
To: Jianfeng Liu <liujianfeng1994@gmail.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 16:02:30 +0800	[thread overview]
Message-ID: <Z8AcFq9bDuW0oiD5@nchen-desktop> (raw)
In-Reply-To: <20250227045236.2830419-1-liujianfeng1994@gmail.com>

On 25-02-27 12:52:36, Jianfeng Liu wrote:
> 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
> 

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.

-- 

Best regards,
Peter


      reply	other threads:[~2025-02-27  8:05 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 ` [PATCH v2 0/6] arm64: Introduce CIX P1 (SKY1) SoC Jianfeng Liu
2025-02-27  8:02   ` Peter Chen [this message]

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=Z8AcFq9bDuW0oiD5@nchen-desktop \
    --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=liujianfeng1994@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).