From: Marek Vasut <marex@nabladev.com>
To: Andrew Lunn <andrew@lunn.ch>, Wei Fang <wei.fang@nxp.com>
Cc: Clark Wang <xiaoning.wang@nxp.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
"David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [net-next,PATCH v2] enetc: Increase eMDIO MDC rate to 2.5 MHz
Date: Fri, 2 Oct 2026 00:43:04 +0200 [thread overview]
Message-ID: <42f7cfb4-d04d-4782-b789-f291d393af2f@nabladev.com> (raw)
In-Reply-To: <0b1e6d29-5054-423c-bf7d-2206f2473579@lunn.ch>
On 10/1/26 3:53 PM, Andrew Lunn wrote:
>> Okay, but please consider Andrew's suggestion. Add clock-frequency
>> support for greater flexibility in adapting to different situations,
>> instead of fixing the MDC clock to 2.5MHz.
>
> I consider this nice to have. And to actually implement it, you need
> to know the base frequency in order to calculate the divider. So i
> suggest the first patches in the patchset set the clock to 2.5Mhz,
> then consider other DT requested frequencies.
I sent this:
[net-next,PATCH] enetc: Set eMDIO MDC rate to 2.5 MHz only on i.MX95
This sets MX95 to 2.5 MHz and keeps other SoCs unaffected.
Wei, for the other SoCs, do we know which SoCs clocks the MDC (divider)
from which clock ? And can we figure out the clock rates and dividers ?
For the MX95, I assume the clock that feed the MDC divider are "enet"
clock at 666 MHz , divided by 66 and divided by 4 ? Where does the 4
come from ?
Thank you for your help !
next prev parent reply other threads:[~2026-10-01 22:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 18:05 [net-next,PATCH v2] enetc: Increase eMDIO MDC rate to 2.5 MHz Marek Vasut
2026-09-25 18:43 ` netdev-bot+sashiko
2026-09-30 2:10 ` patchwork-bot+netdevbpf
2026-09-30 2:21 ` Marek Vasut
2026-09-30 20:51 ` Jakub Kicinski
2026-09-30 3:40 ` Wei Fang
2026-09-30 4:19 ` Marek Vasut
2026-09-30 6:12 ` Wei Fang
2026-09-30 13:11 ` Andrew Lunn
2026-10-01 0:04 ` Wei Fang
2026-09-30 13:27 ` Marek Vasut
2026-10-01 0:45 ` Wei Fang
2026-10-01 1:34 ` Marek Vasut
2026-10-01 10:57 ` Wei Fang
2026-10-01 13:53 ` Andrew Lunn
2026-10-01 22:43 ` Marek Vasut [this message]
2026-10-08 3:08 ` Wei Fang
2026-10-01 22:51 ` Jakub Kicinski
2026-10-01 23:11 ` Marek Vasut
2026-10-01 22:00 ` Marek Vasut
2026-10-08 2:34 ` Wei Fang
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=42f7cfb4-d04d-4782-b789-f291d393af2f@nabladev.com \
--to=marex@nabladev.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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