From: Marek Vasut <marex@nabladev.com>
To: Wei Fang <wei.fang@nxp.com>, Clark Wang <xiaoning.wang@nxp.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: "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:00:29 +0200 [thread overview]
Message-ID: <d8e72848-1611-4d6e-b3e8-17013bce7948@nabladev.com> (raw)
In-Reply-To: <b4addd8f-43ba-417e-85ad-a78391c8f2fb@nabladev.com>
On 9/30/26 3:27 PM, Marek Vasut wrote:
Hello again,
>> Clark helped measure the MDC rate on the 95 EVK board this morning,
>> and the
>> result was 644KHz, which is consistent with the theoretical value. The
>> scope's
>> accuracy or other factors may be causing you to observe a rate of 558kHz.
>
> That 644 kHz and 558 kHz differs too much to be an equipment
> miscalibration / misuse.
For the sake of completeness, the MX95 B0 I have on my desk now prints
this in SM:
>$ clock.r
...
097: busnetcmix = on, 133333333Hz
098: enet = on, 666666666Hz
099: enetphytest200m = on, 24000000Hz
100: enetphytest500m = on, 24000000Hz
101: enetphytest667m = on, 24000000Hz
102: enetref = on, 250000000Hz
103: enettimer1 = on, 24000000Hz
And the cycle time of MDC is 1.8ms , which is some 550 kHz .
prev parent reply other threads:[~2026-10-01 22:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 18:05 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
2026-10-01 22:51 ` Jakub Kicinski
2026-10-01 23:11 ` Marek Vasut
2026-10-01 22:00 ` Marek Vasut [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=d8e72848-1611-4d6e-b3e8-17013bce7948@nabladev.com \
--to=marex@nabladev.com \
--cc=andrew+netdev@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
all inboxes | Powered by JetHome®