From: Yao Zi <me@ziyao.cc>
To: Yixun Lan <dlan@gentoo.org>, Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: Alex Elder <elder@riscstar.com>,
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 2/2] reset: spacemit: fix auxiliary device id
Date: Sat, 20 Dec 2025 02:40:12 +0000 [thread overview]
Message-ID: <aUYMjAi8YIqValwb@pie> (raw)
In-Reply-To: <20251220-06-k1-clk-common-v1-2-df28a0a91621@gentoo.org>
On Sat, Dec 20, 2025 at 09:11:20AM +0800, Yixun Lan wrote:
> Due to the auxiliary register procedure moved to ccu common module,
> the auxiliary device id need to be adjusted, otherwise reset driver
> will fail to probe.
Does it mean the reset driver fails to probe with only PATCH 1 in the
series applied? If so these two patches should probably be merged, or we
will get unfunctional commits.
Regards,
Yao Zi
> Signed-off-by: Yixun Lan <dlan@gentoo.org>
WARNING: multiple messages have this Message-ID (diff)
From: Yao Zi <me@ziyao.cc>
To: Yixun Lan <dlan@gentoo.org>, Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: Alex Elder <elder@riscstar.com>,
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 2/2] reset: spacemit: fix auxiliary device id
Date: Sat, 20 Dec 2025 02:40:12 +0000 [thread overview]
Message-ID: <aUYMjAi8YIqValwb@pie> (raw)
In-Reply-To: <20251220-06-k1-clk-common-v1-2-df28a0a91621@gentoo.org>
On Sat, Dec 20, 2025 at 09:11:20AM +0800, Yixun Lan wrote:
> Due to the auxiliary register procedure moved to ccu common module,
> the auxiliary device id need to be adjusted, otherwise reset driver
> will fail to probe.
Does it mean the reset driver fails to probe with only PATCH 1 in the
series applied? If so these two patches should probably be merged, or we
will get unfunctional commits.
Regards,
Yao Zi
> Signed-off-by: Yixun Lan <dlan@gentoo.org>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-12-20 2:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 1:11 [PATCH 0/2] clk: spacemit: refactor common ccu driver Yixun Lan
2025-12-20 1:11 ` Yixun Lan
2025-12-20 1:11 ` [PATCH 1/2] clk: spacemit: extract common ccu functions Yixun Lan
2025-12-20 1:11 ` Yixun Lan
2025-12-20 1:11 ` [PATCH 2/2] reset: spacemit: fix auxiliary device id Yixun Lan
2025-12-20 1:11 ` Yixun Lan
2025-12-20 2:40 ` Yao Zi [this message]
2025-12-20 2:40 ` Yao Zi
2025-12-20 2:59 ` Yixun Lan
2025-12-20 2:59 ` Yixun Lan
2025-12-24 11:48 ` Yixun Lan
2025-12-24 11:48 ` Yixun Lan
2026-01-03 22:00 ` Yixun Lan
2026-01-03 22:00 ` Yixun Lan
2026-01-08 11:07 ` Philipp Zabel
2026-01-08 11:07 ` Philipp Zabel
2025-12-25 7:47 ` Yixun Lan
2025-12-25 7:47 ` 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=aUYMjAi8YIqValwb@pie \
--to=me@ziyao.cc \
--cc=dlan@gentoo.org \
--cc=elder@riscstar.com \
--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 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.