From: Alex Elder <elder@riscstar.com>
To: Yixun Lan <dlan@gentoo.org>, Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: Guodong Xu <guodong@riscstar.com>,
Inochi Amaoto <inochiama@gmail.com>,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: Re: [PATCH v3 3/4] clk: spacemit: add platform SoC prefix to reset name
Date: Tue, 6 Jan 2026 08:43:56 -0600 [thread overview]
Message-ID: <017413d7-426f-495e-94df-b93e39b0be98@riscstar.com> (raw)
In-Reply-To: <20260103-06-k1-clk-common-v3-3-6061d9f69eef@gentoo.org>
On 1/3/26 1:26 AM, Yixun Lan wrote:
> This change is needed for adding future new SpacemiT K3 reset driver.
>
> Since both K1 and K3 reset code register via the same module which its
> name changed to spacemit_ccu, it's necessary to encode the platform/SoC
> in the reset auxiliary device name to distinguish them, otherwise two
> reset drivers will claim to support same "compatible" auxiliary device
> even in the case of only one CCU clock driver got registered, which in
> the end lead to a broken reset driver.
>
> Signed-off-by: Yixun Lan <dlan@gentoo.org>
Looks good.
Reviewed-by: Alex Elder <elder@riscstar.com>
> ---
> drivers/clk/spacemit/ccu-k1.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/clk/spacemit/ccu-k1.c b/drivers/clk/spacemit/ccu-k1.c
> index 02c792a73759..dee14d25f75d 100644
> --- a/drivers/clk/spacemit/ccu-k1.c
> +++ b/drivers/clk/spacemit/ccu-k1.c
> @@ -789,7 +789,7 @@ static struct clk_hw *k1_ccu_mpmu_hws[] = {
> };
>
> static const struct spacemit_ccu_data k1_ccu_mpmu_data = {
> - .reset_name = "mpmu-reset",
> + .reset_name = "k1-mpmu-reset",
> .hws = k1_ccu_mpmu_hws,
> .num = ARRAY_SIZE(k1_ccu_mpmu_hws),
> };
> @@ -900,7 +900,7 @@ static struct clk_hw *k1_ccu_apbc_hws[] = {
> };
>
> static const struct spacemit_ccu_data k1_ccu_apbc_data = {
> - .reset_name = "apbc-reset",
> + .reset_name = "k1-apbc-reset",
> .hws = k1_ccu_apbc_hws,
> .num = ARRAY_SIZE(k1_ccu_apbc_hws),
> };
> @@ -971,21 +971,21 @@ static struct clk_hw *k1_ccu_apmu_hws[] = {
> };
>
> static const struct spacemit_ccu_data k1_ccu_apmu_data = {
> - .reset_name = "apmu-reset",
> + .reset_name = "k1-apmu-reset",
> .hws = k1_ccu_apmu_hws,
> .num = ARRAY_SIZE(k1_ccu_apmu_hws),
> };
>
> static const struct spacemit_ccu_data k1_ccu_rcpu_data = {
> - .reset_name = "rcpu-reset",
> + .reset_name = "k1-rcpu-reset",
> };
>
> static const struct spacemit_ccu_data k1_ccu_rcpu2_data = {
> - .reset_name = "rcpu2-reset",
> + .reset_name = "k1-rcpu2-reset",
> };
>
> static const struct spacemit_ccu_data k1_ccu_apbc2_data = {
> - .reset_name = "apbc2-reset",
> + .reset_name = "k1-apbc2-reset",
> };
>
> static const struct of_device_id of_k1_ccu_match[] = {
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-01-06 14:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-03 7:26 [PATCH v3 0/4] clk: spacemit: refactor common ccu driver Yixun Lan
2026-01-03 7:26 ` [PATCH v3 1/4] clk: spacemit: prepare common ccu header Yixun Lan
2026-01-06 14:43 ` Alex Elder
2026-01-03 7:26 ` [PATCH v3 2/4] clk: spacemit: extract common ccu functions Yixun Lan
2026-01-06 14:43 ` Alex Elder
2026-01-06 22:27 ` Yixun Lan
2026-01-06 23:42 ` Alex Elder
2026-01-03 7:26 ` [PATCH v3 3/4] clk: spacemit: add platform SoC prefix to reset name Yixun Lan
2026-01-06 14:43 ` Alex Elder [this message]
2026-01-03 7:26 ` [PATCH v3 4/4] reset: spacemit: fix auxiliary device id Yixun Lan
2026-01-06 14:43 ` Alex Elder
2026-01-08 11:07 ` Philipp Zabel
2026-01-08 12:24 ` 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=017413d7-426f-495e-94df-b93e39b0be98@riscstar.com \
--to=elder@riscstar.com \
--cc=dlan@gentoo.org \
--cc=guodong@riscstar.com \
--cc=inochiama@gmail.com \
--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=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