diff options
| author | Robert Hancock <robert.hancock@calian.com> | 2022-04-27 13:39:28 -0600 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2022-05-01 12:03:09 +0100 |
| commit | 0ed99ecc95b9c1d3c46d3bc34459088e82caef32 (patch) | |
| tree | 8719bfedf3df6998406278127925eac0eedd64dc /net/core | |
| parent | 48cec73a891cca087fbc7791c4753784180991a9 (diff) | |
| download | linux-0ed99ecc95b9c1d3c46d3bc34459088e82caef32.tar.gz linux-0ed99ecc95b9c1d3c46d3bc34459088e82caef32.tar.bz2 linux-0ed99ecc95b9c1d3c46d3bc34459088e82caef32.zip | |
net: phy: marvell: update abilities and advertising when switching to SGMII
With some SFP modules, such as Finisar FCLF8522P2BTL, the PHY hardware
strapping defaults to 1000BaseX mode, but the kernel prefers to set them
for SGMII mode. When this happens and the PHY is soft reset, the BMSR
status register is updated, but this happens after the kernel has already
read the PHY abilities during probing. This results in support not being
detected for, and the PHY not advertising support for, 10 and 100 Mbps
modes, preventing the link from working with a non-gigabit link partner.
When the PHY is being configured for SGMII mode, call genphy_read_abilities
again in order to re-read the capabilities, and update the advertising
field accordingly.
Signed-off-by: Robert Hancock <robert.hancock@calian.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/core')
0 files changed, 0 insertions, 0 deletions