diff options
author | Florian Fainelli <f.fainelli@gmail.com> | 2014-09-02 11:17:07 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2014-09-04 23:13:58 -0700 |
commit | 4a804c01635a43ed073893532c058fbaa1f5154e (patch) | |
tree | 6a76d65ac4a4227df062f376173b31f2cdff3abf /kernel | |
parent | a9fe8e29945d56f35235a3a0fba99b4cf181d211 (diff) | |
download | linux-4a804c01635a43ed073893532c058fbaa1f5154e.tar.gz linux-4a804c01635a43ed073893532c058fbaa1f5154e.tar.bz2 linux-4a804c01635a43ed073893532c058fbaa1f5154e.zip |
net: systemport: update UMAC_CMD only when link is detected
When we bring the interface down, phy_stop() will schedule the PHY
state machine to call our link adjustment callback. By the time we do so,
we may have clock gated off the SYSTEMPORT hardware block, and this will
cause bus errors to happen in bcm_sysport_adj_link():
Make sure that we only touch the UMAC_CMD register when there is an
actual link. This is safe to do for two reasons:
- updating the Ethernet MAC registers only make sense when a physical
link is present
- the PHY library state machine first set phydev->link = 0 before
invoking phydev->adjust_link in the PHY_HALTED case
This is a similar fix to the GENET one:
c677ba8b3c47650358572091ed8a6af50bfca877 ("net: bcmgenet: update
UMAC_CMD only when link is detected").
Fixes: 80105befdb4b ("net: systemport: add Broadcom SYSTEMPORT Ethernet MAC driver")
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions