Netdev List
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Michael Walle <mwalle@kernel.org>
Cc: Russell King <linux@armlinux.org.uk>, netdev@vger.kernel.org
Subject: Re: phylink and an unusual PHY/SFP setup
Date: Wed, 27 May 2026 15:35:34 +0200	[thread overview]
Message-ID: <061815ee-e95e-4723-aa2a-d84bc3ad6233@lunn.ch> (raw)
In-Reply-To: <DITB8QZ1OEQF.327XUI9E0SXQ3@kernel.org>

On Wed, May 27, 2026 at 10:19:18AM +0200, Michael Walle wrote:
> Hi,
> 
> I have a board with a rather unusual network link setup:
> 
>  MAC/PCS (fman) <-SerDes-> PHY (M88E1112) <-SerDes-> SFP
> 
> or even
> 
>  MAC/PCS (fman) <-SerDes-> PHY (M88E1112) <-SerDes-> Copper SFP with PHY

Such setups do exist already, but with a different PHY. The Marvel 10G
PHY is sometimes placed in the middle like this. And there are other
PHYs.

Take a look at

commit 35d1a5464b476aa98b7b76ce41bb4de748cebfc2
Author: Maxime Chevallier <maxime.chevallier@bootlin.com>
Date:   Thu Jan 8 09:00:35 2026 +0100

    net: phy: marvell10g: Support SFP through phy_port
    
    Convert the Marvell10G driver to use the generic SFP handling, through a
    dedicated .attach_port() handler to populate the port's supported
    interfaces.
    
    As the 88x3310 supports multiple MDI, the .attach_port() logic handles
    both SFP attach with 10GBaseR support, and support for the "regular"
    port that usually is a BaseT port.

Also, marvell-88x2222.c.

	Andrew

      reply	other threads:[~2026-05-27 13:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27  8:19 phylink and an unusual PHY/SFP setup Michael Walle
2026-05-27 13:35 ` Andrew Lunn [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=061815ee-e95e-4723-aa2a-d84bc3ad6233@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=linux@armlinux.org.uk \
    --cc=mwalle@kernel.org \
    --cc=netdev@vger.kernel.org \
    /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