From: Alex Elder <elder@riscstar.com>
To: mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: p.zabel@pengutronix.de, dlan@gentoo.org, 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: [PATCH v5 0/7] clk: spacemit: add K1 reset support
Date: Fri, 18 Apr 2025 09:53:52 -0500 [thread overview]
Message-ID: <20250418145401.2603648-1-elder@riscstar.com> (raw)
This series adds reset controller support for the SpacemiT K1 SoC.
Most of the the clock controller driver that Haylen Chu had out for
review has been accepted (at v8). So this time this series is
based on the "for-next" branch in the SpacemiT repository:
https://github.com/spacemit-com/linux/tree/for-next
All of these patches are available here:
https://github.com/riscstar/linux/tree/outgoing/reset-v5
Between version 4 and version 5:
- Added Haylen's Reviewed-by on the second patch.
- Added Philipp's Reviewed-by on the third patch.
- In patch 4, added a const qualifier to some structures, and removed
parentheses surrounding integer constants, as suggested by Philipp
- Now based on the SpacemiT for-next branch
Here is version 4 of this series.
https://lore.kernel.org/lkml/20250414191715.2264758-1-elder@riscstar.com/
Between version 3 and version 4:
- Now based on Haylen Chu's v7 clock code, built on v6.15-rc2.
- Added Krzysztof's Reviewed-by on the first patch.
Here is version 3 of this series.
https://lore.kernel.org/lkml/20250409211741.1171584-1-elder@riscstar.com/
Between version 2 and version 3 there was no feedback, however:
- Haylen posted v6 of the clock series, and it included some changes
that affected the logic in this reset code.
- I was informed that defining CCU nodes without any clocks led to
warnings about "clocks" being a required property when running
"make dtbs_check". For that reason, I made clock properties
optional for reset-only CCU nodes.
- This code is now based on v6.15-rc1, which includes a few commits
that were listed as dependencies previously.
Here is version 2 of this series.
https://lore.kernel.org/lkml/20250328210233.1077035-1-elder@riscstar.com/
Between version 1 and version 2:
- Added Rob's Reviewed-by tag on the first patch
- Renamed the of_match_data data type (and one or two other symbols) to
use "spacemit" rather than "k1".
- Replaced the abbreviated "rst" or "RST" in names of newly-defined
sympols with "reset" or "RESET" respectively.
- Eliminated rcdev_to_controller(), which was only used once.
- Changed a function that unsafely did a read/modify/write of a register
to use regmap_update_bits() instead as suggested by Haylen.
- Eliminated a null check for a pointer known to be non-null.
- Reordered the assignment of reset controller device fields.
- Added a "sentinel" comment as requested by Yixun.
- Updated to be based on Linux v6.14 final.
Here is the first version of this series.
https://lore.kernel.org/lkml/20250321151831.623575-1-elder@riscstar.com/
*** BLURB HERE ***
Alex Elder (7):
dt-bindings: soc: spacemit: define spacemit,k1-ccu resets
clk: spacemit: rename spacemit_ccu_data fields
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 | 29 +-
arch/riscv/boot/dts/spacemit/k1.dtsi | 18 +
drivers/clk/spacemit/ccu-k1.c | 330 +++++++++++++++++-
.../dt-bindings/clock/spacemit,k1-syscon.h | 128 +++++++
4 files changed, 482 insertions(+), 23 deletions(-)
base-commit: 279d51ad9f6dc0c667f6f141a669b2c921277d1a
--
2.45.2
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2025-04-18 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 14:53 Alex Elder [this message]
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 ` [PATCH v5 2/7] clk: spacemit: rename spacemit_ccu_data fields Alex Elder
2025-04-18 14:53 ` [PATCH v5 3/7] clk: spacemit: add reset controller support Alex Elder
2025-04-18 14:53 ` [PATCH v5 4/7] clk: spacemit: define existing syscon resets Alex Elder
2025-04-18 14:53 ` [PATCH v5 5/7] clk: spacemit: make clocks optional 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 ` [PATCH v5 7/7] riscv: dts: spacemit: add reset support for the K1 SoC Alex Elder
2025-04-21 13:42 ` [PATCH v5 0/7] clk: spacemit: add K1 reset support Yixun Lan
2025-04-29 20:57 ` Stephen Boyd
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=20250418145401.2603648-1-elder@riscstar.com \
--to=elder@riscstar.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--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 \
--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