DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ivan Malov <ivan.malov@arknetworks.am>
To: dev@dpdk.org
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Andy Moreton <andy.moreton@amd.com>,
	Pieter Jansen Van Vuuren <pieter.jansen-van-vuuren@amd.com>,
	Viacheslav Galaktionov <viacheslav.galaktionov@arknetworks.am>
Subject: [PATCH 0/4] common/sfc_efx/base: link stability improvements for X4 NICs
Date: Fri,  5 Sep 2025 18:45:10 +0400	[thread overview]
Message-ID: <20250905144514.11698-1-ivan.malov@arknetworks.am> (raw)

As announced in [1], this series provides three fixes for link bring-up on
X4 adaptors and an improvement to have link up faster in typical use cases.

[1] https://mails.dpdk.org/archives/dev/2025-August/323545.html

Ivan Malov (4):
  common/sfc_efx/base: fix autoneg detection with netport MCDI
  common/sfc_efx/base: default to auto fcntl with netport MCDI
  common/sfc_efx/base: fix auto FEC selection for netport MCDI
  common/sfc_efx/base: use saved netport FEC choice by default

 drivers/common/sfc_efx/base/efx_impl.h     |  6 +++
 drivers/common/sfc_efx/base/efx_np.c       | 56 +++++++++++++++++-----
 drivers/common/sfc_efx/base/efx_phy.c      |  4 ++
 drivers/common/sfc_efx/base/efx_port.c     |  1 +
 drivers/common/sfc_efx/base/medford4_phy.c |  1 +
 5 files changed, 57 insertions(+), 11 deletions(-)

-- 
2.47.2


             reply	other threads:[~2025-09-05 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05 14:45 Ivan Malov [this message]
2025-09-05 14:45 ` [PATCH 1/4] common/sfc_efx/base: fix autoneg detection with netport MCDI Ivan Malov
2025-09-05 14:45 ` [PATCH 2/4] common/sfc_efx/base: default to auto fcntl " Ivan Malov
2025-09-05 14:45 ` [PATCH 3/4] common/sfc_efx/base: fix auto FEC selection for " Ivan Malov
2025-09-05 14:45 ` [PATCH 4/4] common/sfc_efx/base: use saved netport FEC choice by default Ivan Malov

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=20250905144514.11698-1-ivan.malov@arknetworks.am \
    --to=ivan.malov@arknetworks.am \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=andy.moreton@amd.com \
    --cc=dev@dpdk.org \
    --cc=pieter.jansen-van-vuuren@amd.com \
    --cc=viacheslav.galaktionov@arknetworks.am \
    /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).