From: Yixun Lan <dlan@gentoo.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Alex Elder <elder@riscstar.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Haylen Chu <heylenay@4d2.org>,
linux-clk@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev
Subject: [GIT PULL] clk: spacemit: add changes for v6.17
Date: Wed, 9 Jul 2025 01:15:28 +0000 [thread overview]
Message-ID: <20250709011528-GYA487904@gentoo> (raw)
Hi Stephen,
Here is clock changes for v6.17, please pull.
Basically, what we've added here are two changes:
1) Mark pll1_d8 clock as critical to prevent it from being shut down
in the resource withdrawal path once the probe phase fails
2) Extend K1 clock framework to support reset auxiliary devices, and
also route the reset driver via clock tree to avoid shared tags,
please see discussion here[1] with reset maintainer for more
details if needed.
Thank you!
Link: https://lore.kernel.org/r/3732050b6b756868543012c1a1cebbe7cce74d61.camel@pengutronix.de [1]
Yixun Lan
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
https://github.com/spacemit-com/linux tags/spacemit-clk-for-6.17-1
for you to fetch changes up to c79550f69f0f21be069385c20cd6490b862ba2a5:
Merge tag 'spacemit-reset-for-6.17-1' of https://github.com/spacemit-com/linux (2025-07-07 22:07:15 +0800)
----------------------------------------------------------------
RISC-V SpacemiT clock changes for 6.17
- Mark clock of pll1_d8 as critical
- Add reset support for K1 SoC
----------------------------------------------------------------
Alex Elder (6):
dt-bindings: soc: spacemit: define spacemit,k1-ccu resets
soc: spacemit: create a header for clock/reset registers
clk: spacemit: set up reset auxiliary devices
clk: spacemit: define three reset-only CCUs
clk: spacemit: mark K1 pll1_d8 as critical
reset: spacemit: add support for SpacemiT CCU resets
Yixun Lan (1):
Merge tag 'spacemit-reset-for-6.17-1' of https://github.com/spacemit-com/linux
.../bindings/soc/spacemit/spacemit,k1-syscon.yaml | 27 +-
drivers/clk/spacemit/Kconfig | 1 +
drivers/clk/spacemit/ccu-k1.c | 242 ++++++++--------
drivers/clk/spacemit/ccu_mix.h | 11 +-
drivers/reset/Kconfig | 9 +
drivers/reset/Makefile | 1 +
drivers/reset/reset-spacemit.c | 304 +++++++++++++++++++++
include/dt-bindings/clock/spacemit,k1-syscon.h | 141 ++++++++++
include/soc/spacemit/k1-syscon.h | 160 +++++++++++
9 files changed, 766 insertions(+), 130 deletions(-)
create mode 100644 drivers/reset/reset-spacemit.c
create mode 100644 include/soc/spacemit/k1-syscon.h
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2025-07-09 1:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 1:15 Yixun Lan [this message]
2025-07-13 17:06 ` [GIT PULL] clk: spacemit: add changes for v6.17 Stephen Boyd
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=20250709011528-GYA487904@gentoo \
--to=dlan@gentoo.org \
--cc=elder@riscstar.com \
--cc=heylenay@4d2.org \
--cc=linux-clk@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