From: Haylen Chu <heylenay@4d2.org>
To: Alex Elder <elder@riscstar.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
mturquette@baylibre.com, sboyd@kernel.org,
p.zabel@pengutronix.de, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
dlan@gentoo.org
Cc: 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 v9 3/6] clk: spacemit: set up reset auxiliary devices
Date: Tue, 13 May 2025 05:01:10 +0000 [thread overview]
Message-ID: <aCLSFmSXLUQYi6on@ketchup> (raw)
In-Reply-To: <20250512183212.3465963-4-elder@riscstar.com>
On Mon, May 12, 2025 at 01:32:08PM -0500, Alex Elder wrote:
> Add a new reset_name field to the spacemit_ccu_data structure. If it is
> non-null, the CCU implements a reset controller, and the name will be
> used in the name for the auxiliary device that implements it.
>
> Define a new type to hold an auxiliary device as well as the regmap
> pointer that will be needed by CCU reset controllers. Set up code to
> initialize and add an auxiliary device for any CCU that implements reset
> functionality.
>
> Make it optional for a CCU to implement a clock controller. This
> doesn't apply to any of the existing CCUs but will for some new ones
> that will be added soon.
>
> Signed-off-by: Alex Elder <elder@riscstar.com>
> ---
> v9: Use ida_alloc() to assign the unique auxiliary device ID
>
> drivers/clk/spacemit/Kconfig | 1 +
> drivers/clk/spacemit/ccu-k1.c | 104 ++++++++++++++++++++++++++++---
> include/soc/spacemit/k1-syscon.h | 12 ++++
> 3 files changed, 107 insertions(+), 10 deletions(-)
Reviewed-by: Haylen Chu <heylenay@4d2.org>
next prev parent reply other threads:[~2025-05-13 5:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 18:32 [PATCH v9 0/6] reset: spacemit: add K1 reset support Alex Elder
2025-05-12 18:32 ` [PATCH v9 1/6] dt-bindings: soc: spacemit: define spacemit,k1-ccu resets Alex Elder
2025-05-12 18:32 ` [PATCH v9 2/6] soc: spacemit: create a header for clock/reset registers Alex Elder
2025-05-13 5:02 ` Haylen Chu
2025-05-12 18:32 ` [PATCH v9 3/6] clk: spacemit: set up reset auxiliary devices Alex Elder
2025-05-13 5:01 ` Haylen Chu [this message]
2025-05-12 18:32 ` [PATCH v9 4/6] reset: spacemit: add support for SpacemiT CCU resets Alex Elder
2025-05-13 9:21 ` Philipp Zabel
2025-05-13 12:24 ` Alex Elder
2025-05-12 18:32 ` [PATCH v9 5/6] reset: spacemit: define three more CCUs Alex Elder
2025-05-13 9:21 ` Philipp Zabel
2025-05-13 20:12 ` Yixun Lan
2025-05-13 20:36 ` Alex Elder
2025-05-12 18:32 ` [PATCH v9 6/6] riscv: dts: spacemit: add reset support for the K1 SoC Alex Elder
2025-05-13 20:28 ` [PATCH v9 0/6] reset: spacemit: add K1 reset support 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=aCLSFmSXLUQYi6on@ketchup \
--to=heylenay@4d2.org \
--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=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=p.zabel@pengutronix.de \
--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).