Re: [PATCH v10 0/3] riscv: canaan: Add support for K230 clock

From: Jiayu Du <jiayu.riscv@isrc.iscas.ac.cn>
To: Xukai Wang <kingxukai@zohomail.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	Samuel Holland <samuel.holland@sifive.com>,
	Troy Mitchell <TroyMitchell988@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v10 0/3] riscv: canaan: Add support for K230 clock
Date: Sat, 14 Feb 2026 16:15:22 +0800	[thread overview]
Message-ID: <aZAvGnSrJ7/Ov6wV@duge-virtual-machine> (raw)
In-Reply-To: <283d631f-7cc6-4ec6-9946-5e2120625150@zohomail.com>

On Sat, Feb 14, 2026 at 03:34:16PM +0800, Xukai Wang wrote:
> 
> On 2026/2/14 14:33, Jiayu Du wrote:
> > On Sat, Feb 14, 2026 at 12:37:24AM +0800, Xukai Wang wrote:
> >> On 2026/2/5 00:15, Jiayu Du wrote:
> >>> On Fri, Jan 16, 2026 at 09:26:18PM +0800, Xukai Wang wrote:
> >>>> This patch series adds clock controller support for the Canaan Kendryte
> >>>> K230 SoC. The K230 SoC includes an external 24MHz OSC, 4 internal
> >>>> PLLs and an external pulse input, with the controller managing these
> >>>> sources and their derived clocks.
> >>>  
> >>> Hi, Xukai. Currently, the k230 initial series and the patch 3 of the
> >>> pinctrl series has been in the linux next. So if possible, you need
> >>> to rebase your clock series onto the latest linux-next.
> >>>
> >>> Then I will proceed with the development based on your v11 of the
> >>> clock series.
> >> I've rebased my patch series to `linux-next` (20260212). I noticed that
> >> the patch which updated the `k230.dtsi` format has been merged into
> >> `linux-next`.
> >>
> >> Consequently, I've updated the `prerequisite-patch-id` for my series
> >> from `deda3c472f0000ffd40cddd7cf6d3b5e2d7da7dc` [1] to
> >> `9a2d01f55574b538dad572e193f81c44661f0853` [2]. Is this change correct?
> > Junhui Liu's commit `8cfdbd5e207d434a6e924eb81092874177f97536: riscv: dts:
> > canaan: k230: Add b ISA extension`, also modified k230.dtsi. I'm not
> > sure if you noticed this.
> >
> So, should I use `8cfdbd5e207d434a6e924eb81092874177f97536` as the
> `prerequisite-patch-id` instead of
> `9a2d01f55574b538dad572e193f81c44661f0853`?

Yeah, I think so. Cause the latest modification in linux-next is really
from it.

But actually, you are already using the latest linuxnext version now.
Doesn't it mean that the prerequisite-patch-id might not be necessary?

> >> Link:
> >> https://lore.kernel.org/linux-clk/tencent_F76EB8D731C521C18D5D7C4F8229DAA58E08@qq.com/
> >> [1]
> >> Link:
> >> https://lore.kernel.org/linux-devicetree/20251227092355.42825-1-jiayu.riscv@isrc.iscas.ac.cn/
> >> [2]
> >>
> >> _______________________________________________
> >> linux-riscv mailing list
> >> linux-riscv@lists.infradead.org
> >> http://lists.infradead.org/mailman/listinfo/linux-riscv