[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20201124043440.28400-1-chris.packham@alliedtelesis.co.nz>
Date: Tue, 24 Nov 2020 17:34:36 +1300
From: Chris Packham <chris.packham@...iedtelesis.co.nz>
To: andrew@...n.ch, vivien.didelot@...il.com, f.fainelli@...il.com,
olteanv@...il.com, davem@...emloft.net, kuba@...nel.org,
linux@...linux.org.uk, pavana.sharma@...i.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Chris Packham <chris.packham@...iedtelesis.co.nz>
Subject: [net-next PATCH v5 0/4] net: dsa: mv88e6xxx: serdes link without phy
This small series gets my hardware into a working state. The key points are to
make sure we don't force the link and that we ask the MAC for the link status.
I also have updated my dts to say `phy-mode = "1000base-x";` and `managed =
"in-band-status";`
I've dropped the patch for the 88E6123 as it's a distraction and I lack
hardware to do any proper testing with it. Earlier versions are on the mailing
list if anyone wants to pick it up in the future.
I notice there's a series for mv88e6393x circulating on the netdev mailing
list. As patch #1 is adding a new device specific op either this series will
need updating to cover the mv88e6393x or the mv88e6393x series will need
updating for the new op depenting on which lands first.
Chris Packham (4):
net: dsa: mv88e6xxx: Don't force link when using in-band-status
net: dsa: mv88e6xxx: Support serdes ports on MV88E6097/6095/6185
net: dsa: mv88e6xxx: Add serdes interrupt support for MV88E6097
net: dsa: mv88e6xxx: Handle error in serdes_get_regs
drivers/net/dsa/mv88e6xxx/chip.c | 47 ++++++++++-
drivers/net/dsa/mv88e6xxx/chip.h | 4 +
drivers/net/dsa/mv88e6xxx/port.c | 36 +++++++++
drivers/net/dsa/mv88e6xxx/port.h | 3 +
drivers/net/dsa/mv88e6xxx/serdes.c | 123 +++++++++++++++++++++++++++--
drivers/net/dsa/mv88e6xxx/serdes.h | 9 +++
6 files changed, 213 insertions(+), 9 deletions(-)
--
2.29.2
Powered by blists - more mailing lists