[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <sl752im2sn5sz6yzc23ctprh3rwryuhgtggsaauxixn3b267ag@6sf5fahu6b5i>
Date: Thu, 10 Apr 2025 09:20:33 +0800
From: Inochi Amaoto <inochiama@...il.com>
To: Alex Elder <elder@...cstar.com>, Inochi Amaoto <inochiama@...il.com>,
Yixun Lan <dlan@...too.org>
Cc: Haylen Chu <heylenay@....org>,
Michael Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Haylen Chu <heylenay@...look.com>, Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>,
Alexandre Ghiti <alex@...ti.fr>, linux-riscv@...ts.infradead.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, spacemit@...ts.linux.dev,
Inochi Amaoto <inochiama@...look.com>, Chen Wang <unicornxdotw@...mail.com>,
Jisheng Zhang <jszhang@...nel.org>, Meng Zhang <zhangmeng.kevin@...ux.spacemit.com>
Subject: Re: [PATCH v6 3/6] clk: spacemit: Add clock support for SpacemiT K1
SoC
On Wed, Apr 09, 2025 at 08:10:53PM -0500, Alex Elder wrote:
> On 4/9/25 7:57 PM, Inochi Amaoto wrote:
> > > > > > diff --git a/drivers/clk/spacemit/Kconfig b/drivers/clk/spacemit/Kconfig
> > > > > > new file mode 100644
> > > > > > index 000000000000..4c4df845b3cb
> > > > > > --- /dev/null
> > > > > > +++ b/drivers/clk/spacemit/Kconfig
> > > > > > @@ -0,0 +1,18 @@
> > > > > > +# SPDX-License-Identifier: GPL-2.0-only
> > > > > > +
> > > > > > +config SPACEMIT_CCU
> > > > > > + tristate "Clock support for SpacemiT SoCs"
> > > > > I don't know the answer to this, but... Should this be a Boolean
> > > > > rather than tristate? Can a SpacemiT K1 SoC function without the
> > > > > clock driver built in to the kernel?
> > > > >
> > > > I agree to make it a Boolean, we've already made pinctrl driver Boolean
> > > > and pinctrl depend on clk, besides, the SoC is unlikely functional
> > > > without clock built in as it's such critical..
> > > >
> > > I disagree. The kernel is only for spacemit only, and the pinctrl
> > Sorry for a mistake, this first "only" should be "not".
>
> This is a general problem. You can't make a bootable
> SpacemiT kernel unless you define this as built-in (at
> least, that's what Yixun is saying).
Why not putting the module in the initramfs? I have tested
this in quite a lot of boards (Allwinner, rockchip, sophgo,
starfive and etc.), all of them work well.
> But we'd really rather *only* build it in to the kernel
> for SpacemiT builds. You clearly want to minimize what
> must be built in, but what if this is indeed required?
> What goes in defconfig?
>
As defconfig is more like for a minimum example system. It
is OK to put a y in the defconfig. But for a custom system,
you do give a choice for the builder to remove your module
in non spacemit system.
Regards,
Inochi
Powered by blists - more mailing lists