> -----Original Message----- > From: Andrew Lunn <andrew@xxxxxxx> > Sent: Friday, December 20, 2019 12:06 PM > To: Madalin Bucur (OSS) <madalin.bucur@xxxxxxxxxxx> > Cc: Russell King - ARM Linux admin <linux@xxxxxxxxxxxxxxx>; > antoine.tenart@xxxxxxxxxxxxxxxxxx; jaz@xxxxxxxxxxxx; baruch@xxxxxxxxxx; > davem@xxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx; f.fainelli@xxxxxxxxx; > hkallweit1@xxxxxxxxx; shawnguo@xxxxxxxxxx; devicetree@xxxxxxxxxxxxxxx > Subject: Re: [PATCH 1/6] net: phy: add interface modes for XFI, SFI > > On Fri, Dec 20, 2019 at 09:39:08AM +0000, Madalin Bucur (OSS) wrote: > > > -----Original Message----- > > > From: Andrew Lunn <andrew@xxxxxxx> > > > Sent: Friday, December 20, 2019 11:29 AM > > > To: Russell King - ARM Linux admin <linux@xxxxxxxxxxxxxxx> > > > Cc: Madalin Bucur (OSS) <madalin.bucur@xxxxxxxxxxx>; > antoine.tenart@free- > > > electrons.com; jaz@xxxxxxxxxxxx; baruch@xxxxxxxxxx; > davem@xxxxxxxxxxxxx; > > > netdev@xxxxxxxxxxxxxxx; f.fainelli@xxxxxxxxx; hkallweit1@xxxxxxxxx; > > > shawnguo@xxxxxxxxxx; devicetree@xxxxxxxxxxxxxxx > > > Subject: Re: [PATCH 1/6] net: phy: add interface modes for XFI, SFI > > > > > > > How does this help us when we can't simply change the existing > usage? > > > > We can update the DT but we can't free up the usage of "10gbase-kr". > > > > > > Agreed. Code needs to keep on interpreting "10gbase-kr" as any 10G > > > link. If we ever have a true 10gbase-kr, 802.3ap, one meter of copper > > > and two connectors, we are going to have to add a new mode to > > > represent true 10gbase-kr. > > > > > > Andrew > > > > Hi, actually we do have that. What would be the name of the new mode > > representing true 10GBase-KR that we will need to add when we upstream > > support for that? > > Ah! > > This is going to be messy. > > Do you really need to differentiate? What seems to make 802.3ap > different is the FEC, autoneg and link training. Does you hardware > support this? Do you need to know you are supposed to be using 802.3ap > in order to configure these features? Yes, it does. > What are we going to report to user space? 10gbase-kr, or > 10gbase-kr-true? How do we handle the mess this makes with firmware > based cards which correctly report > ETHTOOL_LINK_MODE_10000baseKR_Full_BIT to user space? > > What do we currently report to user space? Is it possible for us to > split DT from user space? DT says 10gbase-kr-true but to user space we > say ETHTOOL_LINK_MODE_10000baseKR_Full_BIT? > > I think in order to work through these issues, somebody probably needs > the hardware, and the desire to see it working. So it might actually > be you who makes a proposal how we sort this out, with help from > Russell and I. > > Andrew We're overcomplicating the fix. As far as I can see only some Marvell boards declared 10GBase-KR as PHY interface type. These either support 10GBase-KR or they don't. When we learn this, we'll need to set things straight in the device trees and code. Until then it will remain as is, there is no trouble with that. I'll reorder and resend the patches that introduce the XFI and SFI types. Regards, Madalin
