summaryrefslogtreecommitdiffstats
path: root/drivers/cdrom
diff options
context:
space:
mode:
authorFlorian Fainelli <f.fainelli@gmail.com>2015-06-26 10:39:06 -0700
committerDavid S. Miller <davem@davemloft.net>2015-06-28 20:28:20 -0700
commitd8e704e461c217918cf236f49276e469580afbef (patch)
treef0bfdf7d131f89548fd07c506fe41440816656a3 /drivers/cdrom
parent7b635da86821005cd131369b7a4268df8067cc6c (diff)
downloadlinux-d8e704e461c217918cf236f49276e469580afbef.tar.bz2
net: phy: mdio-bcm-unimac: workaround initial read failures for integrated PHYs
All BCM7xxx integrated Gigabit PHYs have an issue in their MDIO management controller which will make the initial read or write to them to fail and return 0xffff. This is a real issue as the typical first thing we do is read from MII_PHYSID1 and MII_PHYSID2 from get_phy_id() to register a driver for these PHYs. Coupled with the workaround in drivers/net/phy/bcm7xxx.c, this workaround for the MDIO bus controller consists in scanning the list of PHYs to do this initial read workaround for as part of the MDIO bus reset routine which is invoked prior to mdiobus_scan(). Once we have a proper PHY driver/device registered, all workarounds are located there (e.g: power management suspend/resume calls). Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/cdrom')
0 files changed, 0 insertions, 0 deletions