After phy_start() phylib takes care of all needed actions, including
aneg settings and checking link state. There's no need to set state
PHY_CHANGELINK in drivers.

Signed-off-by: Heiner Kallweit <hkallwe...@gmail.com>
---
 drivers/net/ethernet/amd/au1000_eth.c | 5 +----
 drivers/net/ethernet/ti/cpmac.c       | 1 -
 2 files changed, 1 insertion(+), 5 deletions(-)

diff --git a/drivers/net/ethernet/amd/au1000_eth.c 
b/drivers/net/ethernet/amd/au1000_eth.c
index 7c1eb304c..e833d1b3f 100644
--- a/drivers/net/ethernet/amd/au1000_eth.c
+++ b/drivers/net/ethernet/amd/au1000_eth.c
@@ -940,11 +940,8 @@ static int au1000_open(struct net_device *dev)
                return retval;
        }
 
-       if (dev->phydev) {
-               /* cause the PHY state machine to schedule a link state check */
-               dev->phydev->state = PHY_CHANGELINK;
+       if (dev->phydev)
                phy_start(dev->phydev);
-       }
 
        netif_start_queue(dev);
 
diff --git a/drivers/net/ethernet/ti/cpmac.c b/drivers/net/ethernet/ti/cpmac.c
index 9b8a30bf9..810dfc7de 100644
--- a/drivers/net/ethernet/ti/cpmac.c
+++ b/drivers/net/ethernet/ti/cpmac.c
@@ -991,7 +991,6 @@ static int cpmac_open(struct net_device *dev)
        cpmac_hw_start(dev);
 
        napi_enable(&priv->napi);
-       dev->phydev->state = PHY_CHANGELINK;
        phy_start(dev->phydev);
 
        return 0;
-- 
2.20.1

Reply via email to