[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bde58941-42f0-73d5-22b3-060349da25c6@gmail.com>
Date: Mon, 30 Apr 2018 12:23:00 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
rmk@...linux.org.uk, linux-kernel@...r.kernel.org,
cphealy@...il.com, nikita.yoush@...entembedded.com,
vivien.didelot@...oirfairelinux.com, Nisar.Sayed@...rochip.com,
UNGLinuxDriver@...rochip.com
Subject: Re: [RFC net-next 0/5] Support for PHY test modes
On 04/30/2018 09:40 AM, Andrew Lunn wrote:
>> Turning these tests on will typically result in the link partner
>> dropping the link with us, and the interface will be non-functional as
>> far as the data path is concerned (similar to an isolation mode). This
>> might warrant properly reporting that to user-space through e.g: a
>> private IFF_* value maybe?
>
> Hi Florian
>
> I've not looked at the code yet....
>
> Is it also necessary to kick off auto-neg again after the test has
> finished, in order to reestablish the link?
It would yes. Right now there is a test mode exposed named "normal"
which really, means: bring back to the PHY to an operation state. This
state likely does not belong here and we would have to introduce flags
instead such as start and stop the test instead.
Please review the patches when we get a chance, because I suspect this
is not the only issue they have ;)
--
Florian
Powered by blists - more mailing lists