From: Philipp Zabel <p.zabel@pengutronix.de>
To: Yixun Lan <dlan@gentoo.org>
Cc: Alex Elder <elder@riscstar.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
mturquette@baylibre.com, sboyd@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, heylenay@4d2.org,
inochiama@outlook.com, guodong@riscstar.com,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
spacemit@lists.linux.dev, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 0/6] reset: spacemit: add K1 reset support
Date: Wed, 02 Jul 2025 12:14:04 +0200 [thread overview]
Message-ID: <0580d4e254705be3765be168ce17c8a1c2e12f8f.camel@pengutronix.de> (raw)
In-Reply-To: <20250702061717-GYA304216@gentoo>
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.
regards
Philipp
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-07-02 10:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 1:11 [PATCH v11 0/6] reset: spacemit: add K1 reset support Alex Elder
2025-06-13 1:11 ` [PATCH v11 1/6] dt-bindings: soc: spacemit: define spacemit,k1-ccu resets Alex Elder
2025-06-13 1:11 ` [PATCH v11 2/6] soc: spacemit: create a header for clock/reset registers Alex Elder
2025-06-13 1:11 ` [PATCH v11 3/6] clk: spacemit: set up reset auxiliary devices Alex Elder
2025-06-13 1:11 ` [PATCH v11 4/6] clk: spacemit: define three reset-only CCUs Alex Elder
2025-06-13 1:11 ` [PATCH v11 5/6] reset: spacemit: add support for SpacemiT CCU resets Alex Elder
2025-06-15 2:44 ` Alex Elder
2025-06-18 11:19 ` Yixun Lan
2025-06-18 11:42 ` Alex Elder
2025-06-13 1:11 ` [PATCH v11 6/6] riscv: dts: spacemit: add reset support for the K1 SoC Alex Elder
2025-06-18 11:17 ` [PATCH v11 0/6] reset: spacemit: add K1 reset support Yixun Lan
2025-07-02 6:17 ` Yixun Lan
2025-07-02 10:14 ` Philipp Zabel [this message]
2025-07-02 10:56 ` Alex Elder
2025-07-03 15:21 ` 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=0580d4e254705be3765be168ce17c8a1c2e12f8f.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=elder@riscstar.com \
--cc=guodong@riscstar.com \
--cc=heylenay@4d2.org \
--cc=inochiama@outlook.com \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).