From: Brian Masney <bmasney@redhat.com>
To: "Stefan Dösinger" <stefandoesinger@gmail.com>
Cc: linux-clk@vger.kernel.org, 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: Re: [GIT PULL] clk: zte: zx297520v3 clock bindings and driver (v2)
Date: Fri, 2 Oct 2026 11:11:51 -0400 [thread overview]
Message-ID: <ar_Jt4eIPy1-uq1-@redhat.com> (raw)
In-Reply-To: <hUBEMGo3TGyVsIj5LaphmQ@gmail.com>
Hi Stefan,
On Thu, Oct 01, 2026 at 08:39:27PM +0300, Stefan Dösinger wrote:
> 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. This is v2 of the pull
> request, based on v7.3-rc1 rather than clk-next.
>
> The patches have been reviewed and carry appropriate R-B tags by
> Krzysztof Kozlowski (bindings) and Brian Masney (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 cee9395acd8043be0644b25c34bfa86623f2b935:
>
> Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
>
> are available in the Git repository at:
>
> https://gitlab.com/stefandoesinger/zx297520-kernel.git tags/v2-zx29-clk-for-7.4
>
> for you to fetch changes up to 75e4151c9e157d84c8c6c365893ecf33d221bca5:
>
> clk: zte: Introduce a driver for zx297520v3 LSP clocks (2026-10-01 20:20:43 +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
The commits in the pull have the changelog in the commit message. For
example:
https://gitlab.com/stefandoesinger/zx297520-kernel/-/commit/75e4151c9e157d84c8c6c365893ecf33d221bca5
I went to the last series and cherry picked the relevant commits.
Brian
WARNING: multiple messages have this Message-ID (diff)
From: Brian Masney <bmasney@redhat.com>
To: "Stefan Dösinger" <stefandoesinger@gmail.com>
Cc: linux-clk@vger.kernel.org, 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: Re: [GIT PULL] clk: zte: zx297520v3 clock bindings and driver (v2)
Date: Fri, 2 Oct 2026 11:11:51 -0400 [thread overview]
Message-ID: <ar_Jt4eIPy1-uq1-@redhat.com> (raw)
In-Reply-To: <hUBEMGo3TGyVsIj5LaphmQ@gmail.com>
Hi Stefan,
On Thu, Oct 01, 2026 at 08:39:27PM +0300, Stefan Dösinger wrote:
> 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. This is v2 of the pull
> request, based on v7.3-rc1 rather than clk-next.
>
> The patches have been reviewed and carry appropriate R-B tags by
> Krzysztof Kozlowski (bindings) and Brian Masney (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 cee9395acd8043be0644b25c34bfa86623f2b935:
>
> Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
>
> are available in the Git repository at:
>
> https://gitlab.com/stefandoesinger/zx297520-kernel.git tags/v2-zx29-clk-for-7.4
>
> for you to fetch changes up to 75e4151c9e157d84c8c6c365893ecf33d221bca5:
>
> clk: zte: Introduce a driver for zx297520v3 LSP clocks (2026-10-01 20:20:43 +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
The commits in the pull have the changelog in the commit message. For
example:
https://gitlab.com/stefandoesinger/zx297520-kernel/-/commit/75e4151c9e157d84c8c6c365893ecf33d221bca5
I went to the last series and cherry picked the relevant commits.
Brian
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-10-02 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 17:39 [GIT PULL] clk: zte: zx297520v3 clock bindings and driver (v2) Stefan Dösinger
2026-10-01 17:39 ` Stefan Dösinger
2026-10-02 15:11 ` Brian Masney [this message]
2026-10-02 15:11 ` Brian Masney
2026-10-02 18:20 ` Stefan Dösinger
2026-10-02 18:20 ` Stefan Dösinger
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=ar_Jt4eIPy1-uq1-@redhat.com \
--to=bmasney@redhat.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=stefandoesinger@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.