From: Yixun Lan <dlan@gentoo.org>
To: Alex Elder <elder@riscstar.com>
Cc: p.zabel@pengutronix.de, mturquette@baylibre.com,
sboyd@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, heylenay@4d2.org, guodong@riscstar.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] clk: spacemit: add K1 reset support
Date: Thu, 20 Mar 2025 23:21:28 +0000 [thread overview]
Message-ID: <20250320232128-GYA10498@gentoo> (raw)
In-Reply-To: <20250320194449.510569-1-elder@riscstar.com>
Hi Alex:
Thanks for sending this patch series
Can you also CC spacemit mailing list: spacemit@lists.linux.dev
it should be handled automaticlly in next 6.15-rc1 version as the
MAINTAINERS file updated
https://web.git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/commit/?id=4a0c4e723c94
On 14:44 Thu 20 Mar , Alex Elder wrote:
> This series adds reset controller support for the SpacemiT K1 SoC.
> It is based on Linux v6.14-rc1.
>
> It is built upon the clock controller driver that Haylen Chu
> currently has out for review (currently at v5):
> https://lore.kernel.org/lkml/20250306175750.22480-2-heylenay@4d2.org/
>
> It also depends on two commits that will land in v6.15: 5728c92ae1123
> ("mfd: syscon: Restore device_node_to_regmap() for non-syscon nodes")
> and 7ff4faba63571 ("pinctrl: spacemit: enable config option").
>
you can use b4 to handle patch dependency, and currently you may got
linux.riscv.bot complaint, but may fix later
https://github.com/linux-riscv/github-ci/issues/24
> The first patch adds three more system controller CCU nodes to those
> implemented by the SpacemiT K1. The second updates the existing clock
> driver with a structure used for OF match data, allowing both clocks
> and resets to be specified. The third provides code that implements
> reset functionality. The fourth defines groups of reset controls
> implemented by the CCUs that have alraady been defined. The fifth
> makes it possible for a CCU to be defined with resets but no clocks.
> The sixth defines three new CCUs which define only resets. And the
> last patch defines these additional syscon nodes in "k1.dtsi".
>
> All of these patches are available here:
> https://github.com/riscstar/linux/tree/outgoing/reset-v1
>
> -Alex
>
> Alex Elder (7):
> dt-bindings: soc: spacemit: define spacemit,k1-ccu resets
> clk: spacemit: define struct k1_ccu_data
> clk: spacemit: add reset controller support
> clk: spacemit: define existing syscon resets
> clk: spacemit: make clocks optional
> clk: spacemit: define new syscons with only resets
> riscv: dts: spacemit: add reset support for the K1 SoC
>
> .../soc/spacemit/spacemit,k1-syscon.yaml | 13 +-
> arch/riscv/boot/dts/spacemit/k1.dtsi | 18 +
> drivers/clk/spacemit/ccu-k1.c | 393 +++++++++++++++++-
> include/dt-bindings/clock/spacemit,k1-ccu.h | 134 ++++++
> 4 files changed, 539 insertions(+), 19 deletions(-)
>
> --
> 2.43.0
>
--
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55
next prev parent reply other threads:[~2025-03-20 23:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 19:44 [PATCH 0/7] clk: spacemit: add K1 reset support Alex Elder
2025-03-20 19:44 ` [PATCH 1/7] dt-bindings: soc: spacemit: define spacemit,k1-ccu resets Alex Elder
2025-03-20 19:44 ` [PATCH 2/7] clk: spacemit: define struct k1_ccu_data Alex Elder
2025-03-20 19:44 ` [PATCH 3/7] clk: spacemit: add reset controller support Alex Elder
2025-03-20 19:44 ` [PATCH 4/7] clk: spacemit: define existing syscon resets Alex Elder
2025-03-20 19:44 ` [PATCH 5/7] clk: spacemit: make clocks optional Alex Elder
2025-03-20 19:44 ` [PATCH 6/7] clk: spacemit: define new syscons with only resets Alex Elder
2025-03-20 19:44 ` [PATCH 7/7] riscv: dts: spacemit: add reset support for the K1 SoC Alex Elder
2025-03-20 23:21 ` Yixun Lan [this message]
2025-03-21 0:05 ` [PATCH 0/7] clk: spacemit: add K1 reset support Alex Elder
2025-03-21 0:16 ` 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=20250320232128-GYA10498@gentoo \
--to=dlan@gentoo.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.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=sboyd@kernel.org \
/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