From: Jakub Kicinski <kuba@kernel.org>
To: Marek Vasut <marex@nabladev.com>
Cc: vladimir.oltean@nxp.com, xiaoning.wang@nxp.com, wei.fang@nxp.com,
claudiu.manoil@nxp.com, netdev@vger.kernel.org,
davem@davemloft.net, andrew+netdev@lunn.ch, edumazet@google.com,
pabeni@redhat.com, imx@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [net-next,PATCH v2] enetc: Increase eMDIO MDC rate to 2.5 MHz
Date: Wed, 30 Sep 2026 13:51:27 -0700 [thread overview]
Message-ID: <20260930135127.28f95804@kernel.org> (raw)
In-Reply-To: <c3b7e841-5eea-4431-b231-44659e1605c3@nabladev.com>
On Wed, 30 Sep 2026 04:21:19 +0200 Marek Vasut wrote:
> On 9/30/26 4:10 AM, patchwork-bot+netdevbpf@kernel.org wrote:
> > Hello:
> >
> > This patch was applied to netdev/net-next.git (main)
> > by Jakub Kicinski <kuba@kernel.org>:
> >
> > On Thu, 24 Sep 2026 20:05:19 +0200 you wrote:
> >> The current eMDIO MDC rate is 558 kHz on i.MX95 B0. This is very low,
> >> but also very compatible. However, for example NXP TJA1120 PHY needs
> >> at minimum 1 MHz MDC clock and 558 kHz does not work with that PHY.
> >>
> >> As a minimum change, increase the MDC clock to 2.5 MHz which matches
> >> the 802.3 specification. Also, even old PHYs like LAN8210Ai, KSZ8794,
> >> DP83822 support up to 2.5 MHz MDC clock frequency, and it covers the
> >> NXP TJA1120 as well. There is no known rationale for why the 558 kHz
> >> was picked when the eMDIO driver was added.
> >>
> > Here is the summary with links:
> > - [net-next,v2] enetc: Increase eMDIO MDC rate to 2.5 MHz
> > https://git.kernel.org/netdev/net-next/c/587acb86d646
> This should have likely been applied only after someone from NXP looked
> at it.
Maybe say that in the commit message next time.
next prev parent reply other threads:[~2026-09-30 20:51 UTC|newest]
Thread overview: 25+ 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:06 ` sashiko-bot
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 [this message]
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-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
2026-10-12 17:05 ` Marek Vasut
2026-10-13 2:17 ` Wei Fang
2026-10-13 15:25 ` Vladimir Oltean
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=20260930135127.28f95804@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@nabladev.com \
--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 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.