Thread (14 messages) 14 messages, 1 author, 12h ago

Re: [PATCH net-next v14 06/10] net: phy: phy_port: Store information about a port's upstream

From: Maxime Chevallier <maxime.chevallier@bootlin.com>
Date: 2026-07-22 09:59:09
Also in: lkml

Hi,

On 7/20/26 19:48, Maxime Chevallier wrote:
MII phy_ports are not meant to be connected directly to a link partner.
They are meant to feed into some media converter devices that will
expose an MDI phy_port, so far we only support SFP modules for that.

In the case an MDI phy_port is backed by an MII port (e.g. a SFP
module's port, backed by the SFP cage port), let's keep track of the
port id of the MII port backing it.

Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Sashiko notices that we may race between phy_attach() and
phy_set_upstream_port() in the SFP case, that's indeed a possibility I'll
address.

Maxime
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help