Re: [PATCH v11 0/6] reset: spacemit: add K1 reset support

[Yixun Lan]

Hi Philipp,

On 12:14 Wed 02 Jul     , Philipp Zabel wrote:
> On Mi, 2025-07-02 at 06:17 +0000, Yixun Lan wrote:
> > Hi Philipp,
> > 
> > On 11:17 Wed 18 Jun     , Yixun Lan wrote:
> > > Hi ALL,
> > >   As the reset driver going through several review cycles,
> > > it becomes quite calm down now, I'd like to request to merge
> > > it into v6.17, because various drivers (pwm, emac..) will depend
> > > on it, even in the worst case if there is problem, I believe Alex
> > > will help to address..
> > > 
> > > Hi Philipp,
> > >   I'd like to query if you willing to take the reset driver -
> > > patch [5/6] through the reset tree? It sounds more intuitive,
> > > which also will avoid potential conflicts with Kconfig/Makefile..
> > >   I've created a prerequisite immutable tag which could be
> > > shared between clock and reset subsytem. It's tag -
> > > spacemit-reset-deps-for-6.17 at SpacemiT's SoC tree [1], which 
> > > effectively are patches [1-4] of this series.
> > > But, to make your life easy, I've also applied patch [5/6] at tag
> > > spacemit-reset-drv-for-6.17 [2] which has a small macro adjustment
> > > requested by Alex at [3]
> > >   Let me know what you think of this, thanks
> > > 
> > Just want to ping this, what do you want from my side to proceed?
> > 
> > or do you want me to send a more formal Pull-Request for [1],
> > then you can apply patch [5/6] (still need to fix the macro of [3])
> 
> Please send a v12, so that the latest modifications are on the list.
> 
> I'd prefer to either pick patches 1 and 5 from the list, or, if you
> provide a tag with only patch 1 to be pulled into both clk and reset
> trees, to merge that and then pick patch 5.
> 
I will prepare a tag of only patch 1, and leave you to pick patch 5.

So in this way, I can handle the reset - take patch 2-4 via clk tree,
and patch 6 via SoC tree..

I've sent a PR here
 https://lore.kernel.org/all/20250703151823-GYA312602@gentoo/ 

-- 
Yixun Lan (dlan)