diff mbox series

[net-next] net: phy: remove preliminary workaround for not loading PHY driver

Message ID 3cd71ea6-7bb1-97b8-d239-3e322533c472@gmail.com
State Accepted
Delegated to: David Miller
Headers show
Series [net-next] net: phy: remove preliminary workaround for not loading PHY driver | expand

Commit Message

Heiner Kallweit Jan. 15, 2019, 8:11 p.m. UTC
This workaround attempt helped for some but not all affected users.
With commit 11287b693d03 ("r8169: load Realtek PHY driver module
before r8169") we have a better workaround now, so we an remove
the first attempt.

Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
---
 drivers/net/phy/phy_device.c | 8 --------
 1 file changed, 8 deletions(-)

Comments

Florian Fainelli Jan. 15, 2019, 10:30 p.m. UTC | #1
On 1/15/19 12:11 PM, Heiner Kallweit wrote:
> This workaround attempt helped for some but not all affected users.
> With commit 11287b693d03 ("r8169: load Realtek PHY driver module
> before r8169") we have a better workaround now, so we an remove
> the first attempt.
> 
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>

Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
David Miller Jan. 17, 2019, 4:57 a.m. UTC | #2
From: Heiner Kallweit <hkallweit1@gmail.com>
Date: Tue, 15 Jan 2019 21:11:14 +0100

> This workaround attempt helped for some but not all affected users.
> With commit 11287b693d03 ("r8169: load Realtek PHY driver module
> before r8169") we have a better workaround now, so we an remove
> the first attempt.
> 
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>

Applied.
diff mbox series

Patch

diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
index 51990002d..a2423cbb2 100644
--- a/drivers/net/phy/phy_device.c
+++ b/drivers/net/phy/phy_device.c
@@ -2250,14 +2250,6 @@  int phy_driver_register(struct phy_driver *new_driver, struct module *owner)
 	new_driver->mdiodrv.driver.remove = phy_remove;
 	new_driver->mdiodrv.driver.owner = owner;
 
-	/* The following works around an issue where the PHY driver doesn't bind
-	 * to the device, resulting in the genphy driver being used instead of
-	 * the dedicated driver. The root cause of the issue isn't known yet
-	 * and seems to be in the base driver core. Once this is fixed we may
-	 * remove this workaround.
-	 */
-	new_driver->mdiodrv.driver.probe_type = PROBE_FORCE_SYNCHRONOUS;
-
 	retval = driver_register(&new_driver->mdiodrv.driver);
 	if (retval) {
 		pr_err("%s: Error %d in registering driver\n",