From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Inochi Amaoto <inochiama@outlook.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Chao Wei <chao.wei@sophgo.com>,
Chen Wang <unicorn_wang@outlook.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: michael.opdenacker@bootlin.com,
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: (subset) [PATCH v9 0/6] riscv: sophgo: add clock support for Sophgo CV1800/SG2000 SoCs
Date: Sun, 14 Apr 2024 11:11:22 +0200 [thread overview]
Message-ID: <a86c6e6d-812b-4777-981b-c747ca601372@bootlin.com> (raw)
In-Reply-To: <IA1PR20MB4953A5ACD22C8CB791C76BABBB0A2@IA1PR20MB4953.namprd20.prod.outlook.com>
Hi Inochi
Thanks for your help!
On 4/14/24 at 08:43, Inochi Amaoto wrote:
>> Hi Michael,
>>
>> I think you boot with the `defconfig` config. This config does
>> not enable the CV1800 clk support. I think you may need to apply
>> [1], which enable the clk driver. Also if you want to test sdhci
>> with real clk, you can try [2]. I test them on the Milk-V Duo S.
>>
>> Regards,
>> Inochi
>>
>> [1] https://lore.kernel.org/all/IA1PR20MB4953CA5D46EA8913B130D502BB052@IA1PR20MB4953.namprd20.prod.outlook.com/
> I make a mistake when reordering the url.
> [1] should be https://lore.kernel.org/all/IA1PR20MB49537E8B2D1FAAA7D5B8BDA2BB052@IA1PR20MB4953.namprd20.prod.outlook.com/
Indeed, I was using the "defconfig" config. Too used to having
everything working with this configuration on RISC-V :-/
Gotcha for the CONFIG_CLK_SOPHGO_CV1800 setting. However, I'm confused.
Why is this setting available in linux-next, but neither in
git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git ("master" and
"for-next") nor in github.com/sophgo/linux.git ("master" and "for-next") ?
What's the tree used to push to linux-next?
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-04-14 9:11 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
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 [this message]
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=a86c6e6d-812b-4777-981b-c747ca601372@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--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=sboyd@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