From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Yangtao Li <frank.li@vivo.com>,
mturquette@baylibre.com, sboyd@kernel.org,
Jisheng Zhang <jszhang@kernel.org>, Wei Fu <wefu@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Icenowy Zheng <uwu@icenowy.me>
Subject: Re: [PATCH 2/3] clk: thead: add support for the T-HEAD TH1520 CCU
Date: Mon, 15 May 2023 08:27:22 +0200 [thread overview]
Message-ID: <fef0ac30-73c1-86a7-e114-0846ba735965@linaro.org> (raw)
In-Reply-To: <20230515054402.27633-3-frank.li@vivo.com>
On 15/05/2023 07:44, Yangtao Li wrote:
> Add support for th1520 in the clock framework.
>
> Cc: Icenowy Zheng <uwu@icenowy.me>
> Cc: Wei Fu <wefu@redhat.com>
> Cc: Jisheng Zhang <jszhang@kernel.org>
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> ---
> drivers/clk/Kconfig | 6 +
> drivers/clk/Makefile | 1 +
> drivers/clk/clk-th1520.c | 999 +++++++++++++++++++++++
> include/dt-bindings/clock/th1520-clock.h | 92 +++
> 4 files changed, 1098 insertions(+)
Please run scripts/checkpatch.pl and fix reported warnings.
Bindings are always separate patches.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-05-15 6:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 5:43 [PATCH 0/3] Add T-HEAD th1520 soc clock support Yangtao Li
2023-05-15 5:43 ` [PATCH 1/3] dt-bindings: clock: Add thead th1520 clock Yangtao Li
2023-05-15 6:22 ` Krzysztof Kozlowski
2023-05-15 6:26 ` Krzysztof Kozlowski
2023-05-15 5:44 ` [PATCH 2/3] clk: thead: add support for the T-HEAD TH1520 CCU Yangtao Li
2023-05-15 6:27 ` Krzysztof Kozlowski [this message]
2023-06-13 1:35 ` Stephen Boyd
2023-08-27 10:37 ` Jisheng Zhang
2023-09-03 22:37 ` Drew Fustini
2023-05-15 5:44 ` [PATCH 3/3] MAINTAINERS: update entry for T-HEAD RISC-V SoC Yangtao Li
2023-05-15 17:15 ` Conor Dooley
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=fef0ac30-73c1-86a7-e114-0846ba735965@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank.li@vivo.com \
--cc=jszhang@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=uwu@icenowy.me \
--cc=wefu@redhat.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;
as well as URLs for NNTP newsgroup(s).