diff options
author | Koen Vandeputte <koen.vandeputte@ncentric.com> | 2019-05-06 14:58:43 +0200 |
---|---|---|
committer | Koen Vandeputte <koen.vandeputte@ncentric.com> | 2019-05-13 19:17:41 +0200 |
commit | 762361a79c8e1873898bbf9724ac58ede7464832 (patch) | |
tree | da140307620445448a1e298bc96a37f4c9bb10e4 /target/linux/brcm63xx/patches-4.9/001-4.12-08-net-phy-Call-bus-reset-after-releasing-PHYs-from-res.patch | |
parent | 06403981e1f2daf6bbcf05f5f2d2205d68240861 (diff) | |
download | upstream-762361a79c8e1873898bbf9724ac58ede7464832.tar.gz upstream-762361a79c8e1873898bbf9724ac58ede7464832.tar.bz2 upstream-762361a79c8e1873898bbf9724ac58ede7464832.zip |
brcm63xx: remove kernel 4.9 support
This target got bumped to 4.14 a long time ago
in commit: 2308b87204206d84b6bf3dbc3d72591611cc6b78
Remove all leftover 4.9 files.
Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
Diffstat (limited to 'target/linux/brcm63xx/patches-4.9/001-4.12-08-net-phy-Call-bus-reset-after-releasing-PHYs-from-res.patch')
-rw-r--r-- | target/linux/brcm63xx/patches-4.9/001-4.12-08-net-phy-Call-bus-reset-after-releasing-PHYs-from-res.patch | 43 |
1 files changed, 0 insertions, 43 deletions
diff --git a/target/linux/brcm63xx/patches-4.9/001-4.12-08-net-phy-Call-bus-reset-after-releasing-PHYs-from-res.patch b/target/linux/brcm63xx/patches-4.9/001-4.12-08-net-phy-Call-bus-reset-after-releasing-PHYs-from-res.patch deleted file mode 100644 index 182ad62bf8..0000000000 --- a/target/linux/brcm63xx/patches-4.9/001-4.12-08-net-phy-Call-bus-reset-after-releasing-PHYs-from-res.patch +++ /dev/null @@ -1,43 +0,0 @@ -From df0c8d911abf6ba97b2c2fc3c5a12769e0b081a3 Mon Sep 17 00:00:00 2001 -From: Florian Fainelli <f.fainelli@gmail.com> -Date: Thu, 11 May 2017 11:24:16 -0700 -Subject: [PATCH] net: phy: Call bus->reset() after releasing PHYs from reset - -The API convention makes it that a given MDIO bus reset should be able -to access PHY devices in its reset() callback and perform additional -MDIO accesses in order to bring the bus and PHYs in a working state. - -Commit 69226896ad63 ("mdio_bus: Issue GPIO RESET to PHYs.") broke that -contract by first calling bus->reset() and then release all PHYs from -reset using their shared GPIO line, so restore the expected -functionality here. - -Fixes: 69226896ad63 ("mdio_bus: Issue GPIO RESET to PHYs.") -Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> -Signed-off-by: David S. Miller <davem@davemloft.net> ---- - drivers/net/phy/mdio_bus.c | 6 +++--- - 1 file changed, 3 insertions(+), 3 deletions(-) - ---- a/drivers/net/phy/mdio_bus.c -+++ b/drivers/net/phy/mdio_bus.c -@@ -330,9 +330,6 @@ int __mdiobus_register(struct mii_bus *b - - mutex_init(&bus->mdio_lock); - -- if (bus->reset) -- bus->reset(bus); -- - /* de-assert bus level PHY GPIO resets */ - if (bus->num_reset_gpios > 0) { - bus->reset_gpiod = devm_kcalloc(&bus->dev, -@@ -362,6 +359,9 @@ int __mdiobus_register(struct mii_bus *b - } - } - -+ if (bus->reset) -+ bus->reset(bus); -+ - for (i = 0; i < PHY_MAX_ADDR; i++) { - if ((bus->phy_mask & (1 << i)) == 0) { - struct phy_device *phydev; |