[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170106162420.GA341@lunn.ch>
Date: Fri, 6 Jan 2017 17:24:20 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Madalin-Cristian Bucur <madalin.bucur@....com>
Cc: Florian Fainelli <f.fainelli@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Fixed link for 10G
On Fri, Jan 06, 2017 at 12:01:06PM +0000, Madalin-Cristian Bucur wrote:
> Hi Florian,
>
> I'm trying to add a fixed-link property that declares 10G speed
> for a XGMII PHY and I'm encountering some issues as the fixed
> link infrastructure does not seem to support this speed.
>
> I'm using this device tree snippet (using the legacy format, but it
> should not matter):
>
> ethernet@...00 { /* 10GEC2 */
> fixed-link = <0 1 10000 0 0>;
> phy-connection-type = "xgmii";
> };
>
> and I get this error:
>
> [ 0.464238] swphy: unknown speed
> [ 0.467464] fsl_mac: probe of 1af2000.ethernet failed with error -22
>
> Looking at the code, fixed_phy_register() seems to check for speeds up
> to 1G and swphy only caters 1G and lower speeds, the swphy_decode_speed()
> returning -EINVAL for 10G, triggering the error printed above in
> swphy_validate_state().
>
> What would be the proper way to add support for the 10G fixed link speed?
Hi Madalin
I came across the same issue a couple of months ago. But i found a
different way to solve my problem.
Anyway, fixed-link emulates a PHY. It has the common PHY registers,
and sets the register values to indicate the device tree
configuration.
As you have found out, it only emulates 10/100/1000. For 10G, you need
to extend the emulation to include the 10G registers. Assuming the 10G
registers are standardised.
Andrew
Powered by blists - more mailing lists