From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Yajun Deng <yajun.deng@linux.dev>,
hkallweit1@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: Synchronize c45_ids to phy_id
Date: Fri, 23 May 2025 18:39:02 +0100 [thread overview]
Message-ID: <aDCytj5c4Mn69Y1D@shell.armlinux.org.uk> (raw)
In-Reply-To: <098e1f6a-1e0f-4819-98d7-146a28110043@lunn.ch>
On Fri, May 23, 2025 at 03:03:43PM +0200, Andrew Lunn wrote:
>
> > > The second point has already been made by Russell, there are lots of
> > >
> > > different C45 IDs, and phylib will try to find a driver based on any
> > >
> > > of them.
> >
> > I noticed that. I tested the BCM89890, 88X3310 and 88Q2110 PHY devices,
> > and the ID is always the same in different MMDs.
>
> Try a Marvel 10G PHY. They have different IDs. It has been speculated
> Marvell licensed part of the PHY from a different vendor, and you see
> the vendors OUI in some locations.
The 88X3310 was listed, but incorrectly as always having the same ID in
each MMD. This is false as stated previously.
Maybe Marvell have updated the 88x3310 to use the same ID throughout
in a later revision, but it certainly is not true with the versions
I have seen.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-05-23 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 13:19 [PATCH net-next] net: phy: Synchronize c45_ids to phy_id Yajun Deng
2025-05-22 13:26 ` Russell King (Oracle)
2025-05-22 13:39 ` Andrew Lunn
2025-05-23 2:10 ` Yajun Deng
2025-05-23 13:03 ` Andrew Lunn
2025-05-23 17:39 ` Russell King (Oracle) [this message]
2025-05-23 17:37 ` Russell King (Oracle)
2025-05-24 1:36 ` Yajun Deng
2025-05-28 6:35 ` kernel test robot
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=aDCytj5c4Mn69Y1D@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yajun.deng@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).