[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20201022012516.18720-1-chris.packham@alliedtelesis.co.nz>
Date: Thu, 22 Oct 2020 14:25:11 +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
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Chris Packham <chris.packham@...iedtelesis.co.nz>
Subject: [PATCH 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 included patch #4 in this series but I don't have anything to test it on.
It's just a guess based on the datasheets. I'd suggest applying patch 1, 2 & 3
and leaving 4 for the mailing list archives.
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: Handle error in serdes_get_regs
net: dsa: mv88e6xxx: Support serdes ports on MV88E6123/6131
drivers/net/dsa/mv88e6xxx/chip.c | 50 +++++++++++-
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 | 122 +++++++++++++++++++++++++++--
drivers/net/dsa/mv88e6xxx/serdes.h | 9 +++
6 files changed, 217 insertions(+), 7 deletions(-)
--
2.28.0
Powered by blists - more mailing lists