From: "Stefan Dösinger" <stefandoesinger@gmail.com>
To: linux-clk@vger.kernel.org
Cc: Brian Masney <bmasney+clk@redhat.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
Manivannan Sadhasivam <mani@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
mturquette@baylibre.com
Subject: [GIT PULL] clk: zte: zx297520v3 clock bindings and driver
Date: Wed, 30 Sep 2026 21:40:12 +0300 [thread overview]
Message-ID: <LTD3_tELRsyCnoeF8FU_TQ@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4525 bytes --]
Hi,
This pull request contains the device tree bindings and clock driver for ZTE
zx297520v3 boards. It contains the next step in adding support for
zx297520v3 boards: Documenting clock and reset manager hardware and
adding drivers for its PLLs and clock tree.
The patches have been reviewed and carry appropriate R-B tags by Krzysztof Kozlowski (bindings) and Conor Dooley (clk driver).
The PR does not contain the MFD, reset and device tree patches. They
will be submitted to the MFD, reset and soc trees respectively. The
clock driver compiles without them, but won't be instantiated without
the MFD parent.
The following changes since commit b1470947e92aeedd522ddb7363369c956e55d6b6:
Merge branch 'clk-pile' into clk-next (2026-09-29 14:14:32 -0400)
are available in the Git repository at:
https://gitlab.com/stefandoesinger/zx297520-kernel.git tags/zx29-clk-for-7.4
for you to fetch changes up to 89e2c0fa481f6a0da23ad5c4dc98bcd940f09fd2:
clk: zte: Introduce a driver for zx297520v3 LSP clocks (2026-09-30 20:03:29 +0300)
----------------------------------------------------------------
clk: zte: Add clock drivers for zx297520v3 SoC
This tag contains the device tree bindings and clock driver for ZTE
zx297520v3 boards. It contains the next step in adding support for
zx297520v3 boards: Documenting clock and reset manager hardware and
adding drivers for its PLLs and clock tree.
The PR does not contain the MFD, reset and device tree patches. They
will be submitted to the MFD, reset and soc trees respectively. The
clock driver compiles without them, but won't be instantiated without
the MFD parent.
----------------------------------------------------------------
Stefan Dösinger (9):
dt-bindings: clk: zte: Add zx297520v3 top clock and reset controller
dt-bindings: clk: zte: Add zx297520v3 matrix clock and reset controller
dt-bindings: clk: zte: Add zx297520v3 LSP clock and reset controller
clk: zte: Add Clock registration infrastructure
clk: zte: Add regmap-based clocks
clk: zte: Add zx PLL support infrastructure
clk: zte: Introduce a driver for zx297520v3 top clocks
clk: zte: Introduce a driver for zx297520v3 matrix clocks
clk: zte: Introduce a driver for zx297520v3 LSP clocks
Documentation/devicetree/bindings/clock/zte,zx297520v3-lspcrm.yaml | 101 ++
Documentation/devicetree/bindings/clock/zte,zx297520v3-matrixcrm.yaml | 98 ++
Documentation/devicetree/bindings/clock/zte,zx297520v3-topcrm.yaml | 122 +++
MAINTAINERS | 7 +
drivers/clk/Kconfig | 1 +
drivers/clk/Makefile | 1 +
drivers/clk/zte/Kconfig | 28 +
drivers/clk/zte/Makefile | 6 +
drivers/clk/zte/clk-regmap.c | 237 +++++
drivers/clk/zte/clk-zx.c | 192 ++++
drivers/clk/zte/clk-zx.h | 137 +++
drivers/clk/zte/clk-zx297520v3.c | 1657 +++++++++++++++++++++++++++++++++
drivers/clk/zte/pll-zx.c | 576 ++++++++++++
include/dt-bindings/clock/zte,zx297520v3-clk.h | 154 +++
include/dt-bindings/phy/zte,zx297520v3-topcrm.h | 12 +
include/dt-bindings/reset/zte,zx297520v3-reset.h | 62 ++
16 files changed, 3391 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/zte,zx297520v3-lspcrm.yaml
create mode 100644 Documentation/devicetree/bindings/clock/zte,zx297520v3-matrixcrm.yaml
create mode 100644 Documentation/devicetree/bindings/clock/zte,zx297520v3-topcrm.yaml
create mode 100644 drivers/clk/zte/Kconfig
create mode 100644 drivers/clk/zte/Makefile
create mode 100644 drivers/clk/zte/clk-regmap.c
create mode 100644 drivers/clk/zte/clk-zx.c
create mode 100644 drivers/clk/zte/clk-zx.h
create mode 100644 drivers/clk/zte/clk-zx297520v3.c
create mode 100644 drivers/clk/zte/pll-zx.c
create mode 100644 include/dt-bindings/clock/zte,zx297520v3-clk.h
create mode 100644 include/dt-bindings/phy/zte,zx297520v3-topcrm.h
create mode 100644 include/dt-bindings/reset/zte,zx297520v3-reset.h
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
next reply other threads:[~2026-09-30 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 18:40 Stefan Dösinger [this message]
2026-09-30 18:45 ` Stefan Dösinger
2026-10-01 0:27 ` Brian Masney
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=LTD3_tELRsyCnoeF8FU_TQ@gmail.com \
--to=stefandoesinger@gmail.com \
--cc=bmasney+clk@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet+clk@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mani@kernel.org \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=vkoul@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
all inboxes | Powered by JetHome®