From: Peng Fan <peng.fan@oss.nxp.com>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/7] arm64: dts: imx8mp-venice-gw702x: reduce RGMII CLK drive strength
Date: Thu, 18 Sep 2025 17:10:23 +0800 [thread overview]
Message-ID: <20250918091023.GC23028@nxa18884-linux.ap.freescale.net> (raw)
In-Reply-To: <20250916153216.1042625-4-tharvey@gateworks.com>
Hi Tim,
On Tue, Sep 16, 2025 at 08:32:12AM -0700, Tim Harvey wrote:
>The i.MX8M Plus EQOS RGMII tracelength is less than 1in and does not
>require a x6 drive strength. Reduce the CLK drive strength to x1 for
>better emissions.
>
>Signed-off-by: Tim Harvey <tharvey@gateworks.com>
>---
> arch/arm64/boot/dts/freescale/imx8mp-venice-gw702x.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/arch/arm64/boot/dts/freescale/imx8mp-venice-gw702x.dtsi b/arch/arm64/boot/dts/freescale/imx8mp-venice-gw702x.dtsi
>index a1232a4f8485..dd9eeb3479fd 100644
>--- a/arch/arm64/boot/dts/freescale/imx8mp-venice-gw702x.dtsi
>+++ b/arch/arm64/boot/dts/freescale/imx8mp-venice-gw702x.dtsi
>@@ -462,7 +462,7 @@ MX8MP_IOMUXC_ENET_TD1__ENET_QOS_RGMII_TD1 0x16
> MX8MP_IOMUXC_ENET_TD2__ENET_QOS_RGMII_TD2 0x16
> MX8MP_IOMUXC_ENET_TD3__ENET_QOS_RGMII_TD3 0x16
> MX8MP_IOMUXC_ENET_TX_CTL__ENET_QOS_RGMII_TX_CTL 0x16
>- MX8MP_IOMUXC_ENET_TXC__CCM_ENET_QOS_CLOCK_GENERATE_TX_CLK 0x16
>+ MX8MP_IOMUXC_ENET_TXC__CCM_ENET_QOS_CLOCK_GENERATE_TX_CLK 0x0
You also changed FSEL from 2 to 0. So I would add this in commit that if this
matches:
Since TXC is not a high frequency clock, use slow slew rate for lower emissions
and better signal quality
Regards
Peng
> >;
> };
>
>--
>2.25.1
>
next prev parent reply other threads:[~2025-09-18 7:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 15:32 [PATCH 0/7] various imx8m*-venice dt fixupes Tim Harvey
2025-09-16 15:32 ` [PATCH 1/7] arm64: dts: freescale: imx8mp-venice-gw7905-2x: remove duplicate usdhc1 props Tim Harvey
2025-09-18 9:13 ` Peng Fan
2025-09-16 15:32 ` [PATCH 2/7] arm64: dts: imx8m{m,n,p}-venice: disable unused clk output for TI PHY Tim Harvey
2025-09-18 9:34 ` Peng Fan
2025-09-16 15:32 ` [PATCH 3/7] arm64: dts: imx8mp-venice-gw702x: reduce RGMII CLK drive strength Tim Harvey
2025-09-18 9:10 ` Peng Fan [this message]
2025-09-16 15:32 ` [PATCH 4/7] arm64: dts: imx8mm-venice-gw700x: " Tim Harvey
2025-09-18 9:11 ` Peng Fan
2025-09-16 15:32 ` [PATCH 5/7] arm64: dts: imx8mm-venice-gw72xx: remove unused sdhc1 pinctrl Tim Harvey
2025-09-18 9:12 ` Peng Fan
2025-09-16 15:32 ` [PATCH 6/7] arm64: dts: imx8mp-venice-gw702x: remove off-board uart Tim Harvey
2025-09-18 9:12 ` Peng Fan
2025-09-16 15:32 ` [PATCH 7/7] arm64: dts: imx8mp-venice-gw702x: remove off-board sdhc1 Tim Harvey
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=20250918091023.GC23028@nxa18884-linux.ap.freescale.net \
--to=peng.fan@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.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