From: Brian Masney <masneyb@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Long Zhao <longzhao@ambarella.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
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 v12 0/6] arm64: add Ambarella CV75 SoC support
Date: Thu, 19 Nov 2026 09:40:52 -0500 [thread overview]
Message-ID: <av8KdBCzXLeNE0BX@x1g10> (raw)
In-Reply-To: <1148990d-dfa6-489d-99f8-4bf4417b2c4c@app.fastmail.com>
On Thu, Nov 19, 2026 at 03:18:26PM +0100, Arnd Bergmann wrote:
> On Thu, Nov 19, 2026, at 11:13, Long Zhao via B4 Relay wrote:
> > Add the Ambarella CV75 SoC and EVK support: the board binding, the
> > RCT clock binding and driver, ARCH_AMBARELLA, the devicetree and
> > MAINTAINERS.
> >
> > Apply the patches in this order:
> >
> > 1. board binding
> > 2. RCT clock binding and clock ID header
> > 3. ARCH_AMBARELLA
> > 4. RCT clock driver
> > 5. CV75 SoC and EVK device tree, plus defconfig
> > 6. MAINTAINERS
> >
> > The ambarella vendor prefix and the CV75 secure scratchpad syscon
> > binding are already in linux-next. This series does not repeat
> > either of them.
> >
> > GPIO, UART and pinctrl bindings and drivers are separate series.
> > This devicetree references those compatibles.
> >
> > Tested on the CV75 EVK. The board boots. That boot used a local tree
> > that also includes the GPIO, UART and pinctrl patches.
>
> I merged this into the soc/newsoc branch now, which may get
> additional SoCs from other vendors for the merge window. This
> should be in linux-next starting tomorrow.
>
> I also pushed the contents out in two branches:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/log/?h=newsoc/ambarella
>
> contains all six patches, while
I pulled the branch with all six patches into clk-next.
Brian
next prev parent reply other threads:[~2026-11-19 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 10:13 [PATCH v12 0/6] arm64: add Ambarella CV75 SoC support Long Zhao via B4 Relay
2026-11-19 10:13 ` [PATCH v12 1/6] dt-bindings: arm: add Ambarella CV75 platforms Long Zhao via B4 Relay
2026-11-19 10:13 ` [PATCH v12 2/6] dt-bindings: clock: add Ambarella CV75 RCT Long Zhao via B4 Relay
2026-11-19 10:13 ` [PATCH v12 3/6] arm64: add ARCH_AMBARELLA Long Zhao via B4 Relay
2026-11-19 10:13 ` [PATCH v12 4/6] clk: ambarella: add CV75 RCT clock controller Long Zhao via B4 Relay
2026-11-19 10:22 ` Andy Shevchenko
2026-11-19 10:13 ` [PATCH v12 5/6] arm64: dts: ambarella: add CV75 SoC and EVK Long Zhao via B4 Relay
2026-11-19 10:13 ` [PATCH v12 6/6] MAINTAINERS: add ARM/AMBARELLA SoC support Long Zhao via B4 Relay
2026-11-19 14:18 ` [PATCH v12 0/6] arm64: add Ambarella CV75 " Arnd Bergmann
2026-11-19 14:40 ` Brian Masney [this message]
2026-11-19 14:30 ` patchwork-bot+linux-soc
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=av8KdBCzXLeNE0BX@x1g10 \
--to=masneyb@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=krzk@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=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