From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
sasha.neftin@intel.com, vitaly.lifshits@intel.com
Subject: [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2024-03-27 (e1000e)
Date: Wed, 27 Mar 2024 11:55:11 -0700 [thread overview]
Message-ID: <20240327185517.2587564-1-anthony.l.nguyen@intel.com> (raw)
This series contains updates to e1000e driver only.
Vitaly adds retry mechanism for some PHY operations to workaround MDI
error and moves SMBus configuration to avoid possible PHY loss.
The following are changes since commit afbf75e8da8ce8a0698212953d350697bb4355a6:
selftests: netdevsim: set test timeout to 10 minutes
and are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue 1GbE
Vitaly Lifshits (2):
e1000e: Workaround for sporadic MDI error on Meteor Lake systems
e1000e: move force SMBUS from enable ulp function to avoid PHY loss
issue
drivers/net/ethernet/intel/e1000e/hw.h | 2 +
drivers/net/ethernet/intel/e1000e/ich8lan.c | 38 ++--
drivers/net/ethernet/intel/e1000e/netdev.c | 18 ++
drivers/net/ethernet/intel/e1000e/phy.c | 182 ++++++++++++--------
drivers/net/ethernet/intel/e1000e/phy.h | 2 +
5 files changed, 161 insertions(+), 81 deletions(-)
--
2.41.0
next reply other threads:[~2024-03-27 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 18:55 Tony Nguyen [this message]
2024-03-27 18:55 ` [PATCH net 1/2] e1000e: Workaround for sporadic MDI error on Meteor Lake systems Tony Nguyen
2024-03-27 18:55 ` [PATCH net 2/2] e1000e: move force SMBUS from enable ulp function to avoid PHY loss issue Tony Nguyen
2024-03-29 2:20 ` [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2024-03-27 (e1000e) 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=20240327185517.2587564-1-anthony.l.nguyen@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sasha.neftin@intel.com \
--cc=vitaly.lifshits@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.