On Sun, Apr 14, 2024 at 11:11:22AM +0200, Michael Opdenacker wrote: > 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@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/ > > I make a mistake when reordering the url. > > [1] should be https://lore.kernel.org/all/IA1PR20MB49537E8B2D1FAAA7D5B8BDA2BB052@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/ > > > Indeed, I was using the "defconfig" config. Too used to having everything > working with this configuration on RISC-V :-/ > I apologize for this mistake. I just forgot this after removing default value in the Kconfig. > 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") ? At now, we only maintain the dts related change, but not the driver code. The driver code is usually applied by the subsystem maintainer. This is why you only see the clk changes in the linux-next. > > What's the tree used to push to linux-next? > As you see, the driver code applied to the clk/for-next. That is the tree used to push.
