devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Peter Chen" <peter.chen@cixtech.com>
Cc: "Krzysztof Kozlowski" <krzk@kernel.org>,
	"Marc Zyngier" <maz@kernel.org>,
	soc@kernel.org, "Rob Herring" <robh@kernel.org>,
	krzk+dt@kernel.org, "Conor Dooley" <conor+dt@kernel.org>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Will Deacon" <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, cix-kernel-upstream@cixtech.com,
	marcin@juszkiewicz.com.pl, kajetan.puchalski@arm.com,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Fugang . duan" <fugang.duan@cixtech.com>
Subject: Re: [PATCH v5 5/6] arm64: dts: cix: add initial CIX P1(SKY1) dts support
Date: Thu, 27 Mar 2025 11:29:19 +0100	[thread overview]
Message-ID: <faa1d8e7-e882-40ea-b64d-2e139121bc38@app.fastmail.com> (raw)
In-Reply-To: <Z-Ua7MK-Kv033uDu@nchen-desktop>

On Thu, Mar 27, 2025, at 10:31, Peter Chen wrote:
> On 25-03-27 09:18:42, Arnd Bergmann wrote:
>> Agreed. The usual arrangement for a new SoC family is to have
>> the minimum set of drivers (uart, clk, pinctrl, regulator,
>> iommu, irqchip) along with the DT bindings and the dts files
>> in one branch and have that go through the SoC tree as part of
>> the soc/newsoc branch. It sounds like in this case we only need
>> uart and a mailbox since the rest are shared with existing
>> firmware based drivers, so this isn't even the worst case
>> but still requires some coordination between subsystem maintainers
>> to ensure that all patches have been properly reviewed before
>> I merge them.
>
> So, in this case, we should add mailbox driver support in this
> series, and once the mailbox maintainer has reviewed mailbox
> driver, all the patches could go your tree?

Yes, exactly. Just make sure you describe this in the submission
for the mailbox driver to make sure everyone understands the
plan. I don't think we've had a mailbox driver as the critical
path for a new platform before, so they would usually go through
the mailbox subsystem tree.

     Arnd

  reply	other threads:[~2025-03-27 10:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24  6:24 [PATCH v5 0/6] arm64: Introduce CIX P1 (SKY1) SoC Peter Chen
2025-03-24  6:24 ` [PATCH v5 1/6] dt-bindings: vendor-prefixes: Add CIX Technology Group Co., Ltd Peter Chen
2025-03-24  6:24 ` [PATCH v5 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC Peter Chen
2025-03-24  6:24 ` [PATCH v5 3/6] arm64: Kconfig: add ARCH_CIX for cix silicons Peter Chen
2025-03-24  6:24 ` [PATCH v5 4/6] arm64: defconfig: Enable CIX SoC Peter Chen
2025-03-24  6:24 ` [PATCH v5 5/6] arm64: dts: cix: add initial CIX P1(SKY1) dts support Peter Chen
2025-03-25 10:52   ` Marc Zyngier
2025-03-26  3:26     ` Peter Chen
2025-03-26  9:12       ` Marc Zyngier
2025-03-27  6:44         ` Peter Chen
2025-03-27  7:16           ` Krzysztof Kozlowski
2025-03-27  8:18             ` Arnd Bergmann
2025-03-27  9:31               ` Peter Chen
2025-03-27 10:29                 ` Arnd Bergmann [this message]
2025-03-27  8:35             ` Peter Chen
2025-03-27  8:40               ` Krzysztof Kozlowski
2025-03-27  9:47                 ` Peter Chen
2025-03-27 13:06                   ` Krzysztof Kozlowski
2025-03-24  6:24 ` [PATCH v5 6/6] MAINTAINERS: Add CIX SoC maintainer entry 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=faa1d8e7-e882-40ea-b64d-2e139121bc38@app.fastmail.com \
    --to=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=fugang.duan@cixtech.com \
    --cc=kajetan.puchalski@arm.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin@juszkiewicz.com.pl \
    --cc=maz@kernel.org \
    --cc=peter.chen@cixtech.com \
    --cc=robh@kernel.org \
    --cc=soc@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).