From: Stephen Boyd <sboyd@kernel.org>
To: Alex Elder <elder@riscstar.com>, Yixun Lan <dlan@gentoo.org>
Cc: mturquette@baylibre.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, p.zabel@pengutronix.de, heylenay@4d2.org,
guodong@riscstar.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
spacemit@lists.linux.dev, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/7] clk: spacemit: add K1 reset support
Date: Tue, 29 Apr 2025 13:57:39 -0700 [thread overview]
Message-ID: <95c672f35d6e5e1ac91feaa5628cf4fe@kernel.org> (raw)
In-Reply-To: <20250421134218-GYA42923@gentoo>
Quoting Yixun Lan (2025-04-21 06:42:18)
> Hi Alex,
> I'm good with this version, but would wait a few more days for
> people to comment before taking them..
>
> Hi Philipp,
> Since these reset patches [3, 4, 6] are sitting on top of clk driver,
> I'd assume you're ok with taking them through clk tree? I'd plan to queue
> them for 6.16.. if yes, would you be able to give an ACK? I'd appreciate!
>
No. Please put the reset driver in drivers/reset to get proper review
from reset maintainers. Use the auxiliary bus to do that when the device
is both a clk and reset controller.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Alex Elder <elder@riscstar.com>, Yixun Lan <dlan@gentoo.org>
Cc: mturquette@baylibre.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, p.zabel@pengutronix.de, heylenay@4d2.org,
guodong@riscstar.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
spacemit@lists.linux.dev, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/7] clk: spacemit: add K1 reset support
Date: Tue, 29 Apr 2025 13:57:39 -0700 [thread overview]
Message-ID: <95c672f35d6e5e1ac91feaa5628cf4fe@kernel.org> (raw)
In-Reply-To: <20250421134218-GYA42923@gentoo>
Quoting Yixun Lan (2025-04-21 06:42:18)
> Hi Alex,
> I'm good with this version, but would wait a few more days for
> people to comment before taking them..
>
> Hi Philipp,
> Since these reset patches [3, 4, 6] are sitting on top of clk driver,
> I'd assume you're ok with taking them through clk tree? I'd plan to queue
> them for 6.16.. if yes, would you be able to give an ACK? I'd appreciate!
>
No. Please put the reset driver in drivers/reset to get proper review
from reset maintainers. Use the auxiliary bus to do that when the device
is both a clk and reset controller.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-04-29 20:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 14:53 [PATCH v5 0/7] clk: spacemit: add K1 reset support Alex Elder
2025-04-18 14:53 ` Alex Elder
2025-04-18 14:53 ` [PATCH v5 1/7] dt-bindings: soc: spacemit: define spacemit,k1-ccu resets Alex Elder
2025-04-18 14:53 ` Alex Elder
2025-04-18 14:53 ` [PATCH v5 2/7] clk: spacemit: rename spacemit_ccu_data fields Alex Elder
2025-04-18 14:53 ` Alex Elder
2025-04-18 14:53 ` [PATCH v5 3/7] clk: spacemit: add reset controller support Alex Elder
2025-04-18 14:53 ` Alex Elder
2025-04-18 14:53 ` [PATCH v5 4/7] clk: spacemit: define existing syscon resets Alex Elder
2025-04-18 14:53 ` Alex Elder
2025-04-18 14:53 ` [PATCH v5 5/7] clk: spacemit: make clocks optional Alex Elder
2025-04-18 14:53 ` Alex Elder
2025-04-18 14:53 ` [PATCH v5 6/7] clk: spacemit: define new syscons with only resets Alex Elder
2025-04-18 14:53 ` Alex Elder
2025-04-18 14:53 ` [PATCH v5 7/7] riscv: dts: spacemit: add reset support for the K1 SoC Alex Elder
2025-04-18 14:53 ` Alex Elder
2025-04-21 13:42 ` [PATCH v5 0/7] clk: spacemit: add K1 reset support Yixun Lan
2025-04-21 13:42 ` Yixun Lan
2025-04-29 20:57 ` Stephen Boyd [this message]
2025-04-29 20:57 ` Stephen Boyd
2025-04-29 21:44 ` Alex Elder
2025-04-29 21:44 ` Alex Elder
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=95c672f35d6e5e1ac91feaa5628cf4fe@kernel.org \
--to=sboyd@kernel.org \
--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=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=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.