[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190207140939.GI32483@lunn.ch>
Date: Thu, 7 Feb 2019 15:09:39 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Maxime Chevallier <maxime.chevallier@...tlin.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
Florian Fainelli <f.fainelli@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
linux-arm-kernel@...ts.infradead.org,
Antoine Tenart <antoine.tenart@...tlin.com>,
thomas.petazzoni@...tlin.com, gregory.clement@...tlin.com,
miquel.raynal@...tlin.com, nadavh@...vell.com, stefanc@...vell.com,
mw@...ihalf.com
Subject: Re: [PATCH net-next v2 04/10] net: phy: Automatically fill the
generic TP, FIBRE and Backplane modes
On Thu, Feb 07, 2019 at 10:49:33AM +0100, Maxime Chevallier wrote:
> PHY advertised and supported linkmodes contain both specific modes such
> as 1000BASET Half/Full and generic ones such as TP that represent a
> class of modes.
>
> Since some modes such as Fibre, TP or Backplane match a wide range of
> specific modes, we can automatically set these bits if one of the
> specific modes it corresponds to is present in the list.
>
> The 'TP' bit is set whenever there's a BaseT linkmode in
> phydev->supported.
>
> The 'FIBRE' bit is set for BaseL, BaseS and BaseE linkmodes.
>
> Finally, the 'Backplane' is set whenever a BaseK mode is supported.
Hi Maxime
Interesting idea.
But what exactly are we supposed to be representing here? That PHY
can do these modes, or that the port exists on the device? The
marvell10g can do fibre, but do all boards have an SFP/SFF, or do some
only have an RJ-45 for TP? Are there boards without TP and just
SFP/SFF?
Is there documentation in ethtool which gives a clue as to what is
expected?
Thanks
Andrew
Powered by blists - more mailing lists