summaryrefslogtreecommitdiffstats
path: root/tools/arch/s390
diff options
context:
space:
mode:
authorRussell King2017-12-15 17:10:20 +0100
committerDavid S. Miller2017-12-18 21:04:44 +0100
commit6623c0fba10ef45b64ca213ad5dec926f37fa9a0 (patch)
tree9014acf95ba1f78fdd01725b8e30f07e66a3bb95 /tools/arch/s390
parentnet: bridge: fix early call to br_stp_change_bridge_id and plug newlink leaks (diff)
downloadkernel-qcow2-linux-6623c0fba10ef45b64ca213ad5dec926f37fa9a0.tar.gz
kernel-qcow2-linux-6623c0fba10ef45b64ca213ad5dec926f37fa9a0.tar.xz
kernel-qcow2-linux-6623c0fba10ef45b64ca213ad5dec926f37fa9a0.zip
net: phy: marvell: avoid pause mode on SGMII-to-Copper for 88e151x
Observed on the 88e1512 in SGMII-to-Copper mode, negotiating pause is unreliable. While the pause bits can be set in the advertisment register, they clear shortly after negotiation with a link partner commences irrespective of the cause of the negotiation. While these bits may be correctly conveyed to the link partner on the first negotiation, a subsequent negotiation (eg, due to negotiation restart by the link partner, or reconnection of the cable) will result in the link partner seeing these bits as zero, while the kernel believes that it has advertised pause modes. This leads to the local kernel evaluating (eg) symmetric pause mode, while the remote end evaluates that we have no pause mode capability. Since we can't guarantee the advertisment, disable pause mode support with this PHY when used in SGMII-to-Copper mode. The 88e1510 in RGMII-to-Copper mode appears to behave correctly. Reviewed-by: Andrew Lunn <andrew@lunn.ch> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/arch/s390')
0 files changed, 0 insertions, 0 deletions