From: Michal Simek <michal.simek@amd.com>
To: linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com
Cc: Harini Katakam <harini.katakam@amd.com>,
Andrew Davis <afd@ti.com>,
Ashok Reddy Soma <ashok.reddy.soma@xilinx.com>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Manikanta Guntupalli <manikanta.guntupalli@amd.com>,
Parth Gajjar <parth.gajjar@amd.com>,
Rob Herring <robh+dt@kernel.org>,
Robert Hancock <robert.hancock@calian.com>,
Vishal Sagar <vishal.sagar@amd.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: zynqmp: Assign TSU clock frequency for GEMs
Date: Mon, 10 Jul 2023 12:06:10 +0200 [thread overview]
Message-ID: <bc160892-6b84-fe20-ec6a-a3f9f7faef11@amd.com> (raw)
In-Reply-To: <3b9285b50a2a4abb136ecb0873343a4e84626581.1686228675.git.michal.simek@amd.com>
On 6/8/23 14:51, Michal Simek wrote:
> From: Harini Katakam <harini.katakam@amd.com>
>
> Allow changing TSU clock for all GEMs. Kria SOM is using this
> functionality that's why set TSU clock frequency as 250MHz (minimum when
> running at 1G) to allow PTP functionality.
>
> Signed-off-by: Harini Katakam <harini.katakam@amd.com>
> Signed-off-by: Michal Simek <michal.simek@amd.com>
> ---
>
> arch/arm64/boot/dts/xilinx/zynqmp-clk-ccf.dtsi | 4 ++++
> arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revA.dtso | 1 +
> arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revB.dtso | 1 +
> 3 files changed, 6 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/xilinx/zynqmp-clk-ccf.dtsi b/arch/arm64/boot/dts/xilinx/zynqmp-clk-ccf.dtsi
> index f04716841a0c..ccaca29200bb 100644
> --- a/arch/arm64/boot/dts/xilinx/zynqmp-clk-ccf.dtsi
> +++ b/arch/arm64/boot/dts/xilinx/zynqmp-clk-ccf.dtsi
> @@ -146,24 +146,28 @@ &gem0 {
> clocks = <&zynqmp_clk LPD_LSBUS>, <&zynqmp_clk GEM0_REF>,
> <&zynqmp_clk GEM0_TX>, <&zynqmp_clk GEM0_RX>,
> <&zynqmp_clk GEM_TSU>;
> + assigned-clocks = <&zynqmp_clk GEM_TSU>;
> };
>
> &gem1 {
> clocks = <&zynqmp_clk LPD_LSBUS>, <&zynqmp_clk GEM1_REF>,
> <&zynqmp_clk GEM1_TX>, <&zynqmp_clk GEM1_RX>,
> <&zynqmp_clk GEM_TSU>;
> + assigned-clocks = <&zynqmp_clk GEM_TSU>;
> };
>
> &gem2 {
> clocks = <&zynqmp_clk LPD_LSBUS>, <&zynqmp_clk GEM2_REF>,
> <&zynqmp_clk GEM2_TX>, <&zynqmp_clk GEM2_RX>,
> <&zynqmp_clk GEM_TSU>;
> + assigned-clocks = <&zynqmp_clk GEM_TSU>;
> };
>
> &gem3 {
> clocks = <&zynqmp_clk LPD_LSBUS>, <&zynqmp_clk GEM3_REF>,
> <&zynqmp_clk GEM3_TX>, <&zynqmp_clk GEM3_RX>,
> <&zynqmp_clk GEM_TSU>;
> + assigned-clocks = <&zynqmp_clk GEM_TSU>;
> };
>
> &gpio {
> diff --git a/arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revA.dtso b/arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revA.dtso
> index e06c6824dea4..ae1b9b2bdbee 100644
> --- a/arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revA.dtso
> +++ b/arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revA.dtso
> @@ -145,6 +145,7 @@ &gem3 { /* required by spec */
> pinctrl-0 = <&pinctrl_gem3_default>;
> phy-handle = <&phy0>;
> phy-mode = "rgmii-id";
> + assigned-clock-rates = <250000000>;
>
> mdio: mdio {
> #address-cells = <1>;
> diff --git a/arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revB.dtso b/arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revB.dtso
> index 030e2c93f0e6..b59e48be6465 100644
> --- a/arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revB.dtso
> +++ b/arch/arm64/boot/dts/xilinx/zynqmp-sck-kv-g-revB.dtso
> @@ -128,6 +128,7 @@ &gem3 { /* required by spec */
> pinctrl-0 = <&pinctrl_gem3_default>;
> phy-handle = <&phy0>;
> phy-mode = "rgmii-id";
> + assigned-clock-rates = <250000000>;
>
> mdio: mdio {
> #address-cells = <1>;
Applied.
M
prev parent reply other threads:[~2023-07-10 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 12:51 Michal Simek
2023-07-10 10:06 ` Michal Simek [this message]
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=bc160892-6b84-fe20-ec6a-a3f9f7faef11@amd.com \
--to=michal.simek@amd.com \
--cc=afd@ti.com \
--cc=ashok.reddy.soma@xilinx.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=git@xilinx.com \
--cc=harini.katakam@amd.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manikanta.guntupalli@amd.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=parth.gajjar@amd.com \
--cc=robert.hancock@calian.com \
--cc=robh+dt@kernel.org \
--cc=vishal.sagar@amd.com \
/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®