aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/net/phy/phylink.c
diff options
context:
space:
mode:
authorRussell King <rmk+kernel@armlinux.org.uk>2019-12-11 10:56:09 +0000
committerDavid S. Miller <davem@davemloft.net>2019-12-11 11:53:41 -0800
commit74c551ca5a0edcc9cf66a3b73fd95b9a8615bfd0 (patch)
tree8d40d72ad4c72c8a37a998fb27085363f5b6b967 /drivers/net/phy/phylink.c
parentnet: sfp: add more extended compliance codes (diff)
downloadlinux-dev-74c551ca5a0edcc9cf66a3b73fd95b9a8615bfd0.tar.xz
linux-dev-74c551ca5a0edcc9cf66a3b73fd95b9a8615bfd0.zip
net: sfp: add module start/stop upstream notifications
When dealing with some copper modules, we can't positively know the module capabilities are until we have probed the PHY. Without the full capabilities, we may end up failing a module that we could otherwise drive with a restricted set of capabilities. An example of this would be a module with a NBASE-T PHY plugged into a host that supports phy interface modes 2500BASE-X and SGMII. The PHY supports 10GBASE-R, 5000BASE-X, 2500BASE-X, SGMII interface modes, which means a subset of the capabilities are compatible with the host. However, reading the module EEPROM leads us to believe that the module only supports ethtool link mode 10GBASE-T, which is incompatible with the host - and thus results in the module being rejected. This patch adds an extra notification which are triggered after the SFP module's PHY probe, and a corresponding notification just before the PHY is removed. 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 'drivers/net/phy/phylink.c')
0 files changed, 0 insertions, 0 deletions