[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190515161250.ewlj5u4gs3pvuay3@shell.armlinux.org.uk>
Date: Wed, 15 May 2019 17:12:50 +0100
From: Russell King - ARM Linux admin <linux@...linux.org.uk>
To: Andrew Lunn <andrew@...n.ch>
Cc: Maxime Chevallier <maxime.chevallier@...tlin.com>,
Florian Fainelli <f.fainelli@...il.com>,
Vivien Didelot <vivien.didelot@...il.com>,
netdev@...r.kernel.org,
"thomas.petazzoni@...tlin.com" <thomas.petazzoni@...tlin.com>,
Antoine Tenart <antoine.tenart@...tlin.com>,
Heiner Kallweit <hkallweit1@...il.com>
Subject: Re: dsa: using multi-gbps speeds on CPU port
On Wed, May 15, 2019 at 03:27:01PM +0200, Andrew Lunn wrote:
> On the master interface, the armada 8040, eth0, you still need
> something. However, if you look at phylink_parse_fixedlink(), it puts
> the speed etc into a phylink_link_state. It never instantiates a
> fixed-phy. So i think that could be expanded to support higher speeds
> without too much trouble. The interesting part is the IOCTL handler.
phylink already supports 2500 and 10G fixed-link (actually, it doesn't
care too much about the speed value, just passing it through), provided
phy_lookup_setting() and the MAC support the speed.
Since it doesn't bother with emulating a set of phy registers, which
then would be read by phylib and translated back to a speed and duplex
for the MAC to use, it's way more flexible when it comes to the old
emulated-phy fixed links code.
What it doesn't do is provide an emulation of C45 PHYs for mii-tool/
mii-diag - ethtool is the way forward, and it supports ethtool for
these speeds.
--
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
Powered by blists - more mailing lists