From: Yixun Lan <dlan@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Yixun Lan <dlan@gentoo.org>,
Michael Turquette <mturquette@baylibre.com>,
Inochi Amaoto <inochiama@gmail.com>,
linux-clk@vger.kernel.org, spacemit@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] clk: spacemit: Updates for v7.2
Date: Tue, 9 Jun 2026 05:28:09 +0000 [thread overview]
Message-ID: <20260609052422-KYC4837748@kernel.org> (raw)
From: Yixun Lan <dlan@gentoo.org>
Hi Stephen,
Please pull SpacemiT's clock changes for v7.2
All clock changes are related to PCIe for K3 SoC.
Hope this isn't too late..
Yixun Lan
The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
are available in the Git repository at:
https://github.com/spacemit-com/linux spacemit-clk-for-7.2-1
for you to fetch changes up to a37c75d7b5bb7f3344b0e639b313ac5ace6244ff:
clk: spacemit: k3: Add PCIe DBI clock (2026-06-02 07:16:59 +0000)
----------------------------------------------------------------
RISC-V SpacemiT clock changes for 7.2
- Switch parent clock of PCIe
- Fix PCIe clock register offset
- Add PCIe DBI clock
----------------------------------------------------------------
Yixun Lan (4):
clk: spacemit: k3: Switch to pll2_d6 as parent for PCIe clock
clk: spacemit: k3: Fix PCIe clock register offset
dt-bindings: soc: spacemit: k3: Add PCIe DBI clock IDs
clk: spacemit: k3: Add PCIe DBI clock
drivers/clk/spacemit/ccu-k3.c | 30 +++++++++++++++++---------
include/dt-bindings/clock/spacemit,k3-clocks.h | 5 +++++
include/soc/spacemit/k3-syscon.h | 4 ++--
3 files changed, 27 insertions(+), 12 deletions(-)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
reply other threads:[~2026-06-09 5:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260609052422-KYC4837748@kernel.org \
--to=dlan@kernel.org \
--cc=dlan@gentoo.org \
--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=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