[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191017214453.18934-2-f.fainelli@gmail.com>
Date: Thu, 17 Oct 2019 14:44:52 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: netdev@...r.kernel.org
Cc: Florian Fainelli <f.fainelli@...il.com>,
Andrew Lunn <andrew@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
linux-kernel@...r.kernel.org (open list), hkallweit1@...il.com,
bcm-kernel-feedback-list@...adcom.com, olteanv@...il.com,
rmk+kernel@...linux.org.uk, cphealy@...il.com,
Jose Abreu <joabreu@...opsys.com>
Subject: [PATCH net-next v2 1/2] net: phy: Use genphy_loopback() by default
The standard way of putting a PHY device into loopback is most often
suitable for testing. This is going to be necessary in a subsequent
patch that adds RGII debugging capability using the loopback feature.
Clause 45 PHYs are not supported through a generic method yet.
Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
---
drivers/net/phy/phy_device.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
index 9d2bbb13293e..7fa728c44632 100644
--- a/drivers/net/phy/phy_device.c
+++ b/drivers/net/phy/phy_device.c
@@ -1513,8 +1513,10 @@ int phy_loopback(struct phy_device *phydev, bool enable)
if (phydev->drv && phydrv->set_loopback)
ret = phydrv->set_loopback(phydev, enable);
- else
+ else if (phydev->is_c45)
ret = -EOPNOTSUPP;
+ else
+ ret = genphy_loopback(phydev, enable);
if (ret)
goto out;
--
2.17.1
Powered by blists - more mailing lists