aboutsummaryrefslogtreecommitdiffstats
path: root/target
diff options
context:
space:
mode:
authorDaniel González Cabanelas <dgcbueu@gmail.com>2021-02-26 20:49:00 +0100
committerÁlvaro Fernández Rojas <noltari@gmail.com>2021-02-26 21:11:19 +0100
commitcbcac4fde8ba476ac20ec14bfa6a3c3d9a8a8c02 (patch)
treeca61d9193c746d6b1e302c74b8750764005aeb04 /target
parentcbcddc9f318607881799e329b327a68c4e76d5cb (diff)
downloadupstream-cbcac4fde8ba476ac20ec14bfa6a3c3d9a8a8c02.tar.gz
upstream-cbcac4fde8ba476ac20ec14bfa6a3c3d9a8a8c02.tar.bz2
upstream-cbcac4fde8ba476ac20ec14bfa6a3c3d9a8a8c02.zip
kernel: b53: update the BCM5365 UID
BCM63XX internal PHYs and BCM5365 SoC internal switch are both using the same phy_driver->phy_id, causing conflicts and unnecessary probes. E.g the BCM63XX phy internal IRQ is lost on the first probe. The full BCM5365 UID is 0x00406370. Use an additional byte to mask the BCM5365 UID to avoid duplicate driver phy_id's. This will fix the IRQ issue in internal BCM63XX PHYs and avoid more conflicts in the future. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
Diffstat (limited to 'target')
-rw-r--r--target/linux/generic/files/drivers/net/phy/b53/b53_mdio.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/target/linux/generic/files/drivers/net/phy/b53/b53_mdio.c b/target/linux/generic/files/drivers/net/phy/b53/b53_mdio.c
index afe2187cd6..98cdbffe73 100644
--- a/target/linux/generic/files/drivers/net/phy/b53/b53_mdio.c
+++ b/target/linux/generic/files/drivers/net/phy/b53/b53_mdio.c
@@ -417,9 +417,9 @@ static struct phy_driver b53_phy_driver_id2 = {
/* BCM5365 */
static struct phy_driver b53_phy_driver_id3 = {
- .phy_id = 0x00406000,
+ .phy_id = 0x00406300,
.name = "Broadcom B53 (3)",
- .phy_id_mask = 0x1ffffc00,
+ .phy_id_mask = 0x1fffff00,
.features = 0,
.probe = b53_phy_probe,
.remove = b53_phy_remove,