[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dd213d56-ab67-0e97-37fb-5c22b28b90e1@gmail.com>
Date: Fri, 19 Oct 2018 11:43:41 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Jose Abreu <jose.abreu@...opsys.com>, Andrew Lunn <andrew@...n.ch>
Cc: "David S. Miller" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Joao Pinto <joao.pinto@...opsys.com>
Subject: Re: C45 Phys and PHY_FORCING state
On 10/19/2018 05:02 AM, Jose Abreu wrote:
> Hello Andrew and Florian,
>
> Currently I have a 10G C45 phy that is fixed at 10G link. This
> version does not support auto negotiation so I'm turning off the
> feature in phydev struct field. I found out that when I do this
> phylib is not composing C45 frames and is instead using C22. This
> is due to call to genphy_udpate_link() which doesn't work on my
> phy because it doesn't support C22.
>
> If I apply attached patch then things work perfectly fine. Can
> you please review it ?
Looks reasonable, I could not find other functions in the state machine
that were not already abstracting the clause type, or letting a driver
callback be called. Can you submit this as a formal patch against
net-next (and not attached, but inline)?
I would suggest creating a helper, e.g: phy_update_link() that way
everything is well namespaced and clear within the state machine itself.
--
Florian
Powered by blists - more mailing lists