All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	laurentiu.tudor@nxp.com, andrew@lunn.ch, f.fainelli@gmail.com
Subject: Re: [PATCH net-next v4 0/5] dpaa2-eth: add MAC/PHY support through phylink
Date: Fri, 22 Nov 2019 00:06:31 +0000	[thread overview]
Message-ID: <20191122000631.GL1344@shell.armlinux.org.uk> (raw)
In-Reply-To: <20191117164924.GI1344@shell.armlinux.org.uk>

On Sun, Nov 17, 2019 at 04:49:24PM +0000, Russell King - ARM Linux admin wrote:
> On Thu, Oct 31, 2019 at 01:18:27AM +0200, Ioana Ciornei wrote:
> > The dpaa2-eth driver now has support for connecting to its associated PHY
> > device found through standard OF bindings. The PHY interraction is handled
> > by PHYLINK and even though, at the moment, only RGMII_* phy modes are
> > supported by the driver, this is just the first step into adding the
> > necessary changes to support the entire spectrum of capabilities.
> 
> Hi,
> 
> You mention that one of the aims here is to eventually support SFPs.
> Do you have a plan to solve the current problem with the DPAA2
> structure, where the physical network interfaces are configured at
> boot time by RCW for their operating mode?
> 
> If you want full SFP support, then you will need to dynamically
> reconfigure the network interfaces.  For example, 10G NBASE-T SFP+
> modules will dynamically switch between 10GBASE-R (XFI), 5000BASE-X,
> 2500BASE-X, and SGMII depending on the copper side link speed.  The
> PHY may also support UXSGMII but it doesn't power up that way and it
> is not known whether it is possible or how to change the interface
> mode to UXSGMII.
> 
> Then there's the whole issue of SGMII vs 1000BASE-X SFPs, and fiber
> channel SFPs that can operate at 2500BASE-X.

The last thing to be aware of WRT SFPs is that not all of those which
use SGMII send the 16-bit configuration word.  There's at least SFP
out there that I have at the moment where the PHY chip on it is not
capable of doing so, due to the way the chip vendor designed the
device - yet it expects to link to a MAC using SGMII at 1G and 100M
rates by forcing the rates on the MAC side.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

      reply	other threads:[~2019-11-22  0:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 23:18 [PATCH net-next v4 0/5] dpaa2-eth: add MAC/PHY support through phylink Ioana Ciornei
2019-10-30 23:18 ` [PATCH net-next v4 1/5] bus: fsl-mc: export device types present on the bus Ioana Ciornei
2019-10-30 23:18 ` [PATCH net-next v4 2/5] bus: fsl-mc: add the fsl_mc_get_endpoint function Ioana Ciornei
2019-11-17 19:42   ` Russell King - ARM Linux admin
2019-10-30 23:18 ` [PATCH net-next v4 3/5] dpaa2-eth: update the TX frame queues on DPNI_IRQ_EVENT_ENDPOINT_CHANGED Ioana Ciornei
2019-10-30 23:18 ` [PATCH net-next v4 4/5] dpaa2-eth: add MAC/PHY support through phylink Ioana Ciornei
2019-11-17 16:13   ` Russell King - ARM Linux admin
2019-11-19 16:22     ` Ioana Ciornei
2019-11-19 17:14       ` Russell King - ARM Linux admin
2019-11-19 17:49         ` Ioana Ciornei
2019-11-17 17:01   ` Russell King - ARM Linux admin
2019-10-30 23:18 ` [PATCH net-next v4 5/5] net: documentation: add docs for MAC/PHY support in DPAA2 Ioana Ciornei
2019-10-31 21:26 ` [PATCH net-next v4 0/5] dpaa2-eth: add MAC/PHY support through phylink David Miller
2019-11-17 16:04 ` Russell King - ARM Linux admin
2019-12-19 10:14   ` Russell King - ARM Linux admin
2019-12-19 14:19     ` Ioana Ciornei
2019-11-17 16:49 ` Russell King - ARM Linux admin
2019-11-22  0:06   ` Russell King - ARM Linux admin [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=20191122000631.GL1344@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=ioana.ciornei@nxp.com \
    --cc=laurentiu.tudor@nxp.com \
    --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 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.