From: Stephen Boyd <sboyd@kernel.org>
To: Albert Ou <aou@eecs.berkeley.edu>, Chao Wei <chao.wei@sophgo.com>,
Chen Wang <unicorn_wang@outlook.com>,
Conor Dooley <conor+dt@kernel.org>,
Inochi Amaoto <inochiama@outlook.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Jisheng Zhang <jszhang@kernel.org>,
Liu Gui <kenneth.liu@sophgo.com>,
Jingbao Qiu <qiujingbao.dlmu@gmail.com>,
dlan@gentoo.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v9 2/6] clk: sophgo: Add clock support for CV1800 SoC
Date: Thu, 11 Apr 2024 00:07:26 -0700 [thread overview]
Message-ID: <8861e9e249e5568116094112c567b141.sboyd@kernel.org> (raw)
In-Reply-To: <IA1PR20MB49534F37F802CAF117364D66BB262@IA1PR20MB4953.namprd20.prod.outlook.com>
Quoting Inochi Amaoto (2024-03-09 01:02:52)
> Add clock definition and driver code for CV1800 SoC.
>
> Signed-off-by: Inochi Amaoto <inochiama@outlook.com>
> Link: https://github.com/milkv-duo/duo-files/blob/6f4e9b8ecb459e017cca1a8df248a19ca70837a3/duo/datasheet/CV180X-Clock-v1.xlsx
> Link: https://github.com/milkv-duo/duo-files/blob/6f4e9b8ecb459e017cca1a8df248a19ca70837a3/duo/datasheet/CV1800B-CV1801B-Preliminary-Datasheet-full-en.pdf
> ---
Applied to clk-next
next prev parent reply other threads:[~2024-04-11 7:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 9:01 [PATCH v9 0/6] riscv: sophgo: add clock support for Sophgo CV1800/SG2000 SoCs Inochi Amaoto
2024-03-09 9:02 ` [PATCH v9 1/6] dt-bindings: clock: sophgo: Add clock controller of SG2000 series SoC Inochi Amaoto
2024-04-11 7:07 ` Stephen Boyd
2024-03-09 9:02 ` [PATCH v9 2/6] clk: sophgo: Add clock support for CV1800 SoC Inochi Amaoto
2024-04-11 7:07 ` Stephen Boyd [this message]
2024-03-09 9:02 ` [PATCH v9 3/6] clk: sophgo: Add clock support for CV1810 SoC Inochi Amaoto
2024-04-11 7:07 ` Stephen Boyd
2024-03-09 9:02 ` [PATCH v9 4/6] clk: sophgo: Add clock support for SG2000 SoC Inochi Amaoto
2024-04-11 7:07 ` Stephen Boyd
2024-03-09 9:02 ` [PATCH v9 5/6] riscv: dts: sophgo: add clock generator for Sophgo CV1800 series SoC Inochi Amaoto
2024-03-09 9:02 ` [PATCH v9 6/6] riscv: dts: sophgo: add uart clock " Inochi Amaoto
2024-03-15 6:19 ` [PATCH v9 0/6] riscv: sophgo: add clock support for Sophgo CV1800/SG2000 SoCs Inochi Amaoto
2024-04-11 7:38 ` (subset) " Inochi Amaoto
2024-04-14 5:56 ` Michael Opdenacker
2024-04-14 6:41 ` Inochi Amaoto
2024-04-14 6:43 ` Inochi Amaoto
2024-04-14 9:11 ` Michael Opdenacker
2024-04-14 9:41 ` Inochi Amaoto
2024-04-15 7:44 ` Michael Opdenacker
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=8861e9e249e5568116094112c567b141.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=chao.wei@sophgo.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=inochiama@outlook.com \
--cc=jszhang@kernel.org \
--cc=kenneth.liu@sophgo.com \
--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=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=qiujingbao.dlmu@gmail.com \
--cc=robh+dt@kernel.org \
--cc=unicorn_wang@outlook.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 read-only IMAP folder(s) and NNTP newsgroup(s).