From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>, Brian Masney <masneyb@kernel.org>
Cc: Long Zhao <longzhao@ambarella.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
soc@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Jerome Brunet <jbrunet@baylibre.com>,
linux-clk@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Conor Dooley <conor+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
devicetree@vger.kernel.org, Long Zhao <zl020895@163.com>,
linux-kernel@vger.kernel.org, Linus Walleij <linusw@kernel.org>
Subject: Re: [PATCH v11 0/5] arm64: add Ambarella CV75 SoC support
Date: Tue, 10 Nov 2026 09:27:34 +0100 [thread overview]
Message-ID: <bbc16906-45e2-4d81-ae81-ad93e87b13be@kernel.org> (raw)
In-Reply-To: <7eeaf54d-2d7d-420c-a34e-eebc6dd0effe@app.fastmail.com>
On 10/11/2026 09:23, Arnd Bergmann wrote:
> On Tue, Nov 10, 2026, at 09:02, Krzysztof Kozlowski wrote:
>> On Mon, Nov 09, 2026 at 08:22:33PM -0500, Brian Masney wrote:
>
>>> - I can then merge patches 3 and 5 into clk-pile.
>>
>> You will have code depending on non-exisitng ARCH_AMBARELLA symbol, but
>> if that's fine for you then sure.
>>
>>>
>>> - The DTS folks will take patch 4.
>>
>> The entire platform is for SoC tree. This sounds ok for
>> me, but I am not sure if Arnd was merging pulls with
>> dependencies. If not, then worse case the arm64 bits will
>> wait a cycle. Anyway, I guess you can take clock bits.
>
> The way I usually handle new SoC families is to have
> a separate branch for those beside the usual dt/driver/defconfig
> updates, possibly for multiple new SoC families, and
> possibly including required drivers. The idea is that
> whatever we merge here has at least a chance to boot
> into an initramfs with a console.
>
> If it can boot without the clk driver, the easiest way
> would be to just keep the clk and arch/arm64 bits
> separate. If the clk driver is required to boot, I would
> suggest having a branch with the two clk patches that
> can get merged (not applied) into both the clk tree
> and the soc/newsoc branch to put the other patches
> on top. This would make sure we only have each commit
> once, but still have a clean history that includes the
> driver in both sides.
>
There is a build dependency - DTS needs clock binding header - so it has
to be second, unless the dependency is decoupled.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-11-10 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 11:06 Long Zhao via B4 Relay
2026-11-05 11:06 ` [PATCH v11 1/5] dt-bindings: arm: add Ambarella CV75 platforms Long Zhao via B4 Relay
2026-11-05 11:06 ` [PATCH v11 2/5] dt-bindings: clock: add Ambarella CV75 RCT Long Zhao via B4 Relay
2026-11-05 11:06 ` [PATCH v11 3/5] clk: ambarella: add CV75 RCT clock controller Long Zhao via B4 Relay
2026-11-05 11:06 ` [PATCH v11 4/5] arm64: ambarella: add ARCH_AMBARELLA and CV75 EVK DT Long Zhao via B4 Relay
2026-11-05 11:06 ` [PATCH v11 5/5] MAINTAINERS: add ARM/AMBARELLA SoC support Long Zhao via B4 Relay
2026-11-10 1:22 ` [PATCH v11 0/5] arm64: add Ambarella CV75 " Brian Masney
2026-11-10 8:02 ` Krzysztof Kozlowski
2026-11-10 8:23 ` Arnd Bergmann
2026-11-10 8:27 ` Krzysztof Kozlowski [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=bbc16906-45e2-4d81-ae81-ad93e87b13be@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longzhao@ambarella.com \
--cc=masneyb@kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=soc@lists.linux.dev \
--cc=will@kernel.org \
--cc=zl020895@163.com \
/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
all inboxes | Powered by JetHome®