Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@gentoo.org>
To: Alex Elder <elder@riscstar.com>
Cc: Stephen Boyd <sboyd@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Guodong Xu <guodong@riscstar.com>,
	Inochi Amaoto <inochiama@gmail.com>,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
	Yao Zi <me@ziyao.cc>
Subject: Re: [PATCH v3 2/4] clk: spacemit: extract common ccu functions
Date: Wed, 7 Jan 2026 06:27:53 +0800	[thread overview]
Message-ID: <20260106222753-GYA2092678@gentoo.org> (raw)
In-Reply-To: <a198d2d2-0c82-4c9d-abca-d17221ef1453@riscstar.com>

Hi Alex,

On 08:43 Tue 06 Jan     , Alex Elder wrote:
> On 1/3/26 1:26 AM, Yixun Lan wrote:
> > Refactor the probe function of SpacemiT's clock, and extract a common ccu
> > file, so new clock driver added in the future can share the same code,
> > which would lower the burden of maintenance. Since this commit changes the
> > module name where the auxiliary device registered, the auxiliary device id
> > need to be adjusted. Idea of the patch comes from the review of K3 clock
> > driver, please refer to this disucssion[1] for more detail.
> 
> Are all of the hunks of moved code moved without change (I
> think so)?  If so I think it's worth mentioning that.  If
> not, you should explain whatever differs, and why.  (I would
yes, no literal changes with this patch except probe() refactored,
and the real effective change is the module name changed which
I mentioned already

> expect the only thing that would have to change is making
> spacemit_ccu_probe() public.)
to make spacemit_ccu_probe() public, we move SoC specific code
out of this function which should have no functionality change..

(I think the above commit message is ok, and would not plan to send
out another version if no serious comment incoming, unless you insist)

> 
> I made one minor comment below.  I didn't verify, but I
> assume this is all just moving the code around, and based
> on that:
> 
> Reviewed-by: Alex Elder <elder@riscstar.com>
> 
[snip]...
> > diff --git a/drivers/clk/spacemit/ccu_common.c b/drivers/clk/spacemit/ccu_common.c
> > index 4412c4104dab..5f05b17f8452 100644
> > --- a/drivers/clk/spacemit/ccu_common.c
> > +++ b/drivers/clk/spacemit/ccu_common.c
> > @@ -1,6 +1,177 @@
> >   // SPDX-License-Identifier: GPL-2.0-only
> >   
> > +#include <linux/clk-provider.h>
> > +#include <linux/device/devres.h>
> > +#include <linux/mfd/syscon.h>
> >   #include <linux/module.h>
> > +#include <linux/of.h>
> > +#include <linux/slab.h>
> > +#include <soc/spacemit/ccu.h>
> > +
> > +#include "ccu_common.h"
> > +
> > +static DEFINE_IDA(auxiliary_ids);
> 
> I'd insert a space here to make the definition above stand out a
> bit more.
> 
do you mean a blank line?
(I could do this while applying this patch since it's quite trivial..)

-- 
Yixun Lan (dlan)

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-01-06 22:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-03  7:26 [PATCH v3 0/4] clk: spacemit: refactor common ccu driver Yixun Lan
2026-01-03  7:26 ` [PATCH v3 1/4] clk: spacemit: prepare common ccu header Yixun Lan
2026-01-06 14:43   ` Alex Elder
2026-01-03  7:26 ` [PATCH v3 2/4] clk: spacemit: extract common ccu functions Yixun Lan
2026-01-06 14:43   ` Alex Elder
2026-01-06 22:27     ` Yixun Lan [this message]
2026-01-06 23:42       ` Alex Elder
2026-01-03  7:26 ` [PATCH v3 3/4] clk: spacemit: add platform SoC prefix to reset name Yixun Lan
2026-01-06 14:43   ` Alex Elder
2026-01-03  7:26 ` [PATCH v3 4/4] reset: spacemit: fix auxiliary device id Yixun Lan
2026-01-06 14:43   ` Alex Elder
2026-01-08 11:07     ` Philipp Zabel
2026-01-08 12:24       ` Yixun Lan

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=20260106222753-GYA2092678@gentoo.org \
    --to=dlan@gentoo.org \
    --cc=elder@riscstar.com \
    --cc=guodong@riscstar.com \
    --cc=inochiama@gmail.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=me@ziyao.cc \
    --cc=mturquette@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=sboyd@kernel.org \
    --cc=spacemit@lists.linux.dev \
    /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