Updated patchset.
Split the patch to separate mv88e6393 changes from refactoring
serdes_get_lane.
Update Documentation before adding new mode.
Is the 6191X part of the 6193 family? Not the 6390, like the 6191 is?
Or do we have the 6191 in the wrong family?
quoted
+ MV88E6193X,
You don't add any _ops structure for the 6193x. How is it different?
Can you make your best guess at the ops structure. Also, what about
the 6191X?
6393 Family lists 6191X, 6193X and 6393X products. Unlike 6390, the
6393X have 10G interconnect.
I'm not sure on naming of 6191 and 6191X.
I am adding _ops for 6193X, mv88e6193x_ops which can be used for the
other two products unless any specific functionality differs.
Pavana Sharma (4):
dt-bindings: net: Add 5GBASER phy interface mode
net: phy: Add 5GBASER interface mode
net: dsa: mv88e6xxx: Add support for mv88e6393x family of Marvell
net: dsa: mv88e6xxx: Change serdes lane parameter from u8 to int
.../bindings/net/ethernet-controller.yaml | 2 +
drivers/net/dsa/mv88e6xxx/chip.c | 119 ++++++-
drivers/net/dsa/mv88e6xxx/chip.h | 20 +-
drivers/net/dsa/mv88e6xxx/global1.h | 2 +
drivers/net/dsa/mv88e6xxx/global2.h | 8 +
drivers/net/dsa/mv88e6xxx/port.c | 240 +++++++++++++-
drivers/net/dsa/mv88e6xxx/port.h | 43 ++-
drivers/net/dsa/mv88e6xxx/serdes.c | 295 +++++++++++++++---
drivers/net/dsa/mv88e6xxx/serdes.h | 89 ++++--
include/linux/phy.h | 3 +
10 files changed, 733 insertions(+), 88 deletions(-)
--
2.17.1