[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250513201208-GYA518096@gentoo>
Date: Tue, 13 May 2025 20:12:08 +0000
From: Yixun Lan <dlan@...too.org>
To: Philipp Zabel <p.zabel@...gutronix.de>
Cc: Alex Elder <elder@...cstar.com>, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, mturquette@...libre.com, sboyd@...nel.org,
paul.walmsley@...ive.com, palmer@...belt.com, aou@...s.berkeley.edu,
alex@...ti.fr, heylenay@....org, inochiama@...look.com,
guodong@...cstar.com, devicetree@...r.kernel.org,
linux-clk@...r.kernel.org, spacemit@...ts.linux.dev,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v9 5/6] reset: spacemit: define three more CCUs
Hi Philipp,
On 11:21 Tue 13 May , Philipp Zabel wrote:
> On Mo, 2025-05-12 at 13:32 -0500, Alex Elder wrote:
> > Three more CCUs on the SpacemiT K1 SoC implement only resets, not clocks.
> > Define these resets so they can be used.
> >
> > Signed-off-by: Alex Elder <elder@...cstar.com>
> > ---
> > drivers/clk/spacemit/ccu-k1.c | 24 +++++++++++++++
> > drivers/reset/reset-spacemit.c | 51 ++++++++++++++++++++++++++++++++
> > include/soc/spacemit/k1-syscon.h | 30 +++++++++++++++++++
>
> Could you split this into clk: and reset: parts? The reset changes are
>
Do you have suggestion how we should merge the patch series in future?
What I can think of
1) take patch 1, 2, 3 via clock tree, and provide an immutable tag
2) pull the tag, and take all driver/reset via reset tree, and provide an immutable tag back?
3) take the split part of drivers/clock/ in this one via clock tree
> Reviewed-by: Philipp Zabel <p.zabel@...gutronix.de>
>
> regards
> Philipp
>
--
Yixun Lan (dlan)
Powered by blists - more mailing lists