From: Krzysztof Kozlowski <krzk@kernel.org>
To: longzhao@ambarella.com,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org
Cc: Jerome Brunet <jbrunet@baylibre.com>,
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>,
devicetree@vger.kernel.org, Long Zhao <zl020895@163.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: clock: add Ambarella CV75 RCT
Date: Fri, 9 Oct 2026 13:32:00 +0200 [thread overview]
Message-ID: <3bf2dbd1-51c5-4e50-ae97-b9de97320746@kernel.org> (raw)
In-Reply-To: <20261009-cv75-clk-v1-1-6959b4da83c5@ambarella.com>
On 09/10/2026 13:00, Long Zhao via B4 Relay wrote:
> From: Long Zhao <longzhao@ambarella.com>
>
> Document the CV75 RCT clock controller and the clock ID header used by
> DT consumers.
>
> Document #reset-cells for the RCT reset-provider role. Soft-reset line
> IDs and the reset provider driver are deferred; this series has no
> resets= consumers.
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> Signed-off-by: Long Zhao <longzhao@ambarella.com>
> ---
> .../bindings/clock/ambarella,cv75-rct.yaml | 64 ++++++++++++++++++++++
> include/dt-bindings/clock/ambarella,cv75-rct.h | 14 +++++
> 2 files changed, 78 insertions(+)
This should not be split from original patchset.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-09 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 11:00 [PATCH 0/2] clk: add Ambarella CV75 RCT clock controller Long Zhao via B4 Relay
2026-10-09 11:00 ` [PATCH 1/2] dt-bindings: clock: add Ambarella CV75 RCT Long Zhao via B4 Relay
2026-10-09 11:32 ` Krzysztof Kozlowski [this message]
2026-10-09 11:00 ` [PATCH 2/2] clk: ambarella: add CV75 RCT clock controller Long Zhao via B4 Relay
2026-10-09 17:02 ` Brian Masney
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=3bf2dbd1-51c5-4e50-ae97-b9de97320746@kernel.org \
--to=krzk@kernel.org \
--cc=andriy.shevchenko@linux.intel.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=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=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®