From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: andrew@lunn.ch, vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, kuba@kernel.org,
linux@armlinux.org.uk, pavana.sharma@digi.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [net-next PATCH v5 0/4] net: dsa: mv88e6xxx: serdes link without phy
Date: Tue, 24 Nov 2020 17:34:36 +1300 [thread overview]
Message-ID: <20201124043440.28400-1-chris.packham@alliedtelesis.co.nz> (raw)
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
next reply other threads:[~2020-11-24 4:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 4:34 Chris Packham [this message]
2020-11-24 4:34 ` [net-next PATCH v5 1/4] net: dsa: mv88e6xxx: Don't force link when using in-band-status Chris Packham
2020-11-25 0:33 ` Andrew Lunn
2020-11-24 4:34 ` [net-next PATCH v5 2/4] net: dsa: mv88e6xxx: Support serdes ports on MV88E6097/6095/6185 Chris Packham
2020-11-24 4:34 ` [net-next PATCH v5 3/4] net: dsa: mv88e6xxx: Add serdes interrupt support for MV88E6097 Chris Packham
2020-11-25 1:20 ` Andrew Lunn
2020-11-24 4:34 ` [net-next PATCH v5 4/4] net: dsa: mv88e6xxx: Handle error in serdes_get_regs Chris Packham
2020-11-26 2:10 ` [net-next PATCH v5 0/4] net: dsa: mv88e6xxx: serdes link without phy patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201124043440.28400-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pavana.sharma@digi.com \
--cc=vivien.didelot@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).