Re: [PATCH net-next 0/2] net: phy: make PHY_HALTED a transition state to PHY_READY

2018-12-20 Thread David Miller
From: Heiner Kallweit Date: Wed, 19 Dec 2018 07:50:43 +0100 > PHY_HALTED and PHY_READY both are non-started states and quite similar. > Major difference is that phy_start() changes from PHY_HALTED to > PHY_RESUMING which doesn't reconfigure aneg (what PHY_UP does). > > There's no guarantee that

Re: [PATCH net-next 0/2] net: phy: make PHY_HALTED a transition state to PHY_READY

2018-12-19 Thread David Miller
From: Heiner Kallweit Date: Wed, 19 Dec 2018 07:50:43 +0100 > PHY_HALTED and PHY_READY both are non-started states and quite similar. > Major difference is that phy_start() changes from PHY_HALTED to > PHY_RESUMING which doesn't reconfigure aneg (what PHY_UP does). > > There's no guarantee that

[PATCH net-next 0/2] net: phy: make PHY_HALTED a transition state to PHY_READY

2018-12-18 Thread Heiner Kallweit
PHY_HALTED and PHY_READY both are non-started states and quite similar. Major difference is that phy_start() changes from PHY_HALTED to PHY_RESUMING which doesn't reconfigure aneg (what PHY_UP does). There's no guarantee that PHY registers are completely untouched when waking up from power-down, e