Support for RollBall 10G copper SFP modules
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest3 patches 4 repliesIn review
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | net: phy: mdio-i2c: support I2C MDIO protocol for RollBall SFP modulesdrivers/ | +186 | 2 replies | |
| 2/3 | net: phy: sfp: add support for multigig RollBall modulesdrivers/ | +63 | 2 replies | |
| 3/3 | net: phylink: don't fail attaching phy on 1000base-x/2500base-x modedrivers/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH russell-kings-net-queue v2 0/3] Support for RollBall 10G copper SFP modules
Hi Russell,
this series should apply on linux-arm git repository, on branch net-queue.
Some internet providers are already starting to offer 2.5G copper connectivity to their users. On Turris Omnia the SFP port is capable of 2.5G speed, so we tested some copper SFP modules.
This adds support to the SFP subsystem for 10G RollBall copper modules which contain a Marvell 88X3310 PHY. By default these modules are configured in 10GKR only mode on the host interface, and also contain some bad information in EEPROM (the extended_cc byte).
The PHY in these modules is also accessed via a different I2C protocol than the standard one.
Patch 1 adds support for this different I2C MDIO bus.
Patch 2 adds support for these modules into the SFP driver. Patch 3 changes phylink code so that a PHY can be attached even though 802.3z mode is requested.
Marek
Marek Behún (3):
net: phy: mdio-i2c: support I2C MDIO protocol for RollBall SFP modules
net: phy: sfp: add support for multigig RollBall modules
net: phylink: don't fail attaching phy on 1000base-x/2500base-x mode
drivers/net/phy/mdio-i2c.c | 196 +++++++++++++++++++++++++++++++++++-- drivers/net/phy/phylink.c | 4 +- drivers/net/phy/sfp.c | 69 +++++++++++-- 3 files changed, 250 insertions(+), 19 deletions(-)
base-commit: a32e90737c1c92653767d3c95c63c16b9b72c6c2
Signature · 1 line
2.26.2