Re: [PATCH] net: phy: handle state correctly in phy_stop_machine

2017-03-24 Thread David Miller
From: Zach Brown Date: Wed, 22 Mar 2017 15:27:01 -0500 > From: Nathan Sullivan > > If the PHY is halted on stop, then do not set the state to PHY_UP. This > ensures the phy will be restarted later in phy_start when the machine is > started again. > > Signed-off-by: Nathan Sullivan > Signed-o

Re: [PATCH] net: phy: handle state correctly in phy_stop_machine

2017-03-23 Thread Florian Fainelli
On 03/23/2017 02:41 PM, Florian Fainelli wrote: > On 03/22/2017 01:27 PM, Zach Brown wrote: >> From: Nathan Sullivan >> >> If the PHY is halted on stop, then do not set the state to PHY_UP. This >> ensures the phy will be restarted later in phy_start when the machine is >> started again. > > So

Re: [PATCH] net: phy: handle state correctly in phy_stop_machine

2017-03-23 Thread Florian Fainelli
On 03/22/2017 01:27 PM, Zach Brown wrote: > From: Nathan Sullivan > > If the PHY is halted on stop, then do not set the state to PHY_UP. This > ensures the phy will be restarted later in phy_start when the machine is > started again. So essentially what you want to "defeat" here is entering phy

Re: [PATCH] net: phy: handle state correctly in phy_stop_machine

2017-03-23 Thread David Miller
From: Zach Brown Date: Wed, 22 Mar 2017 15:27:01 -0500 > From: Nathan Sullivan > > If the PHY is halted on stop, then do not set the state to PHY_UP. This > ensures the phy will be restarted later in phy_start when the machine is > started again. > > Signed-off-by: Nathan Sullivan > Signed-o

[PATCH] net: phy: handle state correctly in phy_stop_machine

2017-03-22 Thread Zach Brown
From: Nathan Sullivan If the PHY is halted on stop, then do not set the state to PHY_UP. This ensures the phy will be restarted later in phy_start when the machine is started again. Signed-off-by: Nathan Sullivan Signed-off-by: Brad Mouring Acked-by: Xander Huff Acked-by: Kyle Roeschley ---