From: Mario Limonciello <mario.limonciello@dell.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
intel-wired-lan@lists.osuosl.org
Cc: linux-kernel@vger.kernel.org, darcari@redhat.com,
Yijun.Shen@dell.com, Perry.Yuan@dell.com,
Mario Limonciello <mario.limonciello@dell.com>
Subject: [PATCH 0/3] Improve s0ix flows for systems i219LM
Date: Sun, 27 Sep 2020 23:40:21 -0500 [thread overview]
Message-ID: <20200928044024.7595-1-mario.limonciello@dell.com> (raw)
commit e086ba2fccda ("e1000e: disable s0ix entry and exit flows for ME systems")
disabled s0ix flows for systems that have various incarnations of the
i219-LM ethernet controller. This was done because of some regressions
caused by an earlier
commit 632fbd5eb5b0e ("e1000e: fix S0ix flows for cable connected case")
with i219-LM controller.
Performing suspend to idle with these ethernet controllers requires a properly
configured system. To make enabling such systems easier, this patch
series offers configuration options to enable/disable the flows.
The flows have also been confirmed to be configured correctly on Dell's Latitude
and Precision CML systems containing the i219-LM controller, when the kernel also
contains the fix for s0i3.2 entry here:
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20200914/021361.html
Patches 2 and 3 will turn the behavior on by default for Dell's CML systems.
These patches should only be carried if that patch linked above is also applied.
Mario Limonciello (3):
e1000e: allow turning s0ix flows on for systems with ME
e1000e: Add Dell's Comet Lake systems into s0ix heuristics
e1000e: Add more Dell CML systems into s0ix heuristics
.../device_drivers/ethernet/intel/e1000e.rst | 23 ++
drivers/net/ethernet/intel/Kconfig | 1 +
drivers/net/ethernet/intel/e1000e/e1000.h | 7 +
drivers/net/ethernet/intel/e1000e/netdev.c | 64 +++---
drivers/net/ethernet/intel/e1000e/param.c | 209 ++++++++++++++++++
5 files changed, 266 insertions(+), 38 deletions(-)
--
2.25.1
next reply other threads:[~2020-09-28 4:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 4:40 Mario Limonciello [this message]
2020-09-28 4:40 ` [PATCH 1/3] e1000e: allow turning s0ix flows on for systems with ME Mario Limonciello
2020-10-22 19:21 ` [Intel-wired-lan] " Brown, Aaron F
2020-09-28 4:40 ` [PATCH 2/3] e1000e: Add Dell's Comet Lake systems into s0ix heuristics Mario Limonciello
2020-10-07 0:21 ` [Intel-wired-lan] " Brown, Aaron F
2020-10-07 0:29 ` Limonciello, Mario
2020-10-13 16:03 ` Shen, Yijun
2020-09-28 4:40 ` [PATCH 3/3] e1000e: Add more Dell CML " Mario Limonciello
2020-10-07 0:21 ` [Intel-wired-lan] " Brown, Aaron F
2020-10-21 14:49 ` Shen, Yijun
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=20200928044024.7595-1-mario.limonciello@dell.com \
--to=mario.limonciello@dell.com \
--cc=Perry.Yuan@dell.com \
--cc=Yijun.Shen@dell.com \
--cc=darcari@redhat.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).