From: Tom Lendacky <thomas.lendacky@amd.com>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>
Subject: [PATCH net 0/3] amd-xgbe: AMD XGBE driver fixes 2018-04-23
Date: Mon, 23 Apr 2018 11:42:58 -0500 [thread overview]
Message-ID: <20180423164258.18740.98574.stgit@tlendack-t1.amdoffice.net> (raw)
This patch series addresses some issues in the AMD XGBE driver.
The following fixes are included in this driver update series:
- Improve KR auto-negotiation and training (2 patches)
- Add pre and post auto-negotiation hooks
- Use the pre and post auto-negotiation hooks to disable CDR tracking
during auto-negotiation page exchange in KR mode
- Check for SFP tranceiver signal support and only use the signal if the
SFP indicates that it is supported
This patch series is based on net.
---
Please queue this patch series up to stable releases 4.14 and above.
Tom Lendacky (3):
amd-xgbe: Add pre/post auto-negotiation phy hooks
amd-xgbe: Improve KR auto-negotiation and training
amd-xgbe: Only use the SFP supported transceiver signals
drivers/net/ethernet/amd/xgbe/xgbe-common.h | 8 +
drivers/net/ethernet/amd/xgbe/xgbe-debugfs.c | 16 ++
drivers/net/ethernet/amd/xgbe/xgbe-main.c | 1
drivers/net/ethernet/amd/xgbe/xgbe-mdio.c | 24 +++
drivers/net/ethernet/amd/xgbe/xgbe-pci.c | 2
drivers/net/ethernet/amd/xgbe/xgbe-phy-v2.c | 196 ++++++++++++++++++++++++--
drivers/net/ethernet/amd/xgbe/xgbe.h | 9 +
7 files changed, 233 insertions(+), 23 deletions(-)
--
Tom Lendacky
next reply other threads:[~2018-04-23 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 16:42 Tom Lendacky [this message]
2018-04-23 16:43 ` [PATCH net 1/3] amd-xgbe: Add pre/post auto-negotiation phy hooks Tom Lendacky
2018-04-23 16:43 ` [PATCH net 2/3] amd-xgbe: Improve KR auto-negotiation and training Tom Lendacky
2018-04-23 16:43 ` [PATCH net 3/3] amd-xgbe: Only use the SFP supported transceiver signals Tom Lendacky
2018-04-24 1:24 ` [PATCH net 0/3] amd-xgbe: AMD XGBE driver fixes 2018-04-23 David Miller
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=20180423164258.18740.98574.stgit@tlendack-t1.amdoffice.net \
--to=thomas.lendacky@amd.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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