[lkml]   [2018]   [Mar]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/2] net: phy: relax error checking when creating sysfs link netdev->phydev
On March 16, 2018 11:42:21 AM PDT, Grygorii Strashko <> wrote:
>On 03/16/2018 12:34 PM, Florian Fainelli wrote:
>> On 03/16/2018 10:22 AM, Andrew Lunn wrote:
>>> On Wed, Mar 14, 2018 at 05:26:22PM -0500, Grygorii Strashko wrote:
>>>> Some ethernet drivers (like TI CPSW) may connect and manage >1 Net
>PHYs per
>>>> one netdevice, as result such drivers will produce warning during
>>>> boot and fail to connect second phy to netdevice when PHYLIB
>>>> will try to create sysfs link netdev->phydev for second PHY
>>>> in phy_attach_direct(), because sysfs link with the same name has
>>>> created already for the first PHY.
>>>> As result, second CPSW external port will became unusable.
>>>> This issue was introduced by commits:
>>>> 5568363f0cb3 ("net: phy: Create sysfs reciprocal links for
>>>> a3995460491d ("net: phy: Relax error checking on
>>> I wonder if it would be better to add a flag to the phydev that
>>> indicates it is the second PHY connected to a MAC? Add a bit to
>>> phydrv->mdiodrv.flags. If that bit is set, don't create the sysfs
>>> file.
>> We could indeed do that, I am fine with Grygorii's approach though in
>> making the creation more silent and non fatal.
>The link phydev->netdev still can be created. And failure to create
>is non fatal error in my opinion.

They should not be fatal I agree, but it's nice to know when you are doing something wrong anyway.

>>> For 99% of MAC drivers, having two PHYs is an error, so we want to
>>> debug by reporting the sysfs error.
>> That is true, either way is fine with me, really.
>Error still will be reported, just not warning and it will be
>So, with this patch set it will be possible now to continue boot (NFS
>for example),
>connect to the system and gather logs.

The point Andrew is trying to make is that you address one particular failure in the PHY creation path when using > 1 PHY devices with a network device. Using a flag would easily allow us to be more future proof with other parts of PHYLIB for your particular use case if that becomes necessary. This gives you less incentive to fix this use case though.


 \ /
  Last update: 2018-03-16 20:12    [W:0.115 / U:19.260 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site