aboutsummaryrefslogtreecommitdiffstats
path: root/net/tipc/socket.c
diff options
context:
space:
mode:
authorRafał Miłecki <[email protected]>2017-10-12 08:21:26 +0000
committerDavid S. Miller <[email protected]>2017-10-13 05:59:38 +0000
commit12acd136913ccdf394eeb2bc8686ff5505368119 (patch)
treed104e37e5f425f6eeec2fbd8518d2a6d537fe1a0 /net/tipc/socket.c
parentnet: phy: broadcom: support new device flag for setting master mode (diff)
downloadkernel-12acd136913ccdf394eeb2bc8686ff5505368119.tar.gz
kernel-12acd136913ccdf394eeb2bc8686ff5505368119.zip
net: bgmac: enable master mode for BCM54210E and B50212E PHYs
There are 4 very similar PHYs: 0x600d84a1: BCM54210E (rev B0) 0x600d84a2: BCM54210E (rev B1) 0x600d84a5: B50212E (rev B0) 0x600d84a6: B50212E (rev B1) that need setting master mode manually. It's because they run in slave mode by default with Automatic Slave/Master configuration disabled which can lead to unreliable connection with massive ping loss. So far it was reported for a board with BCM47189 SoC and B50212E B1 PHY connected to the bgmac supported ethernet device. Telling PHY driver to setup PHY properly solves this issue. Signed-off-by: Rafał Miłecki <[email protected]> Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'net/tipc/socket.c')
0 files changed, 0 insertions, 0 deletions