From: "Brown, Aaron F" <aaron.f.brown@intel.com>
To: Mario Limonciello <mario.limonciello@dell.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Cc: "Perry.Yuan@dell.com" <Perry.Yuan@dell.com>,
"Yijun.Shen@dell.com" <Yijun.Shen@dell.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [Intel-wired-lan] [PATCH 1/3] e1000e: allow turning s0ix flows on for systems with ME
Date: Thu, 22 Oct 2020 19:21:04 +0000 [thread overview]
Message-ID: <DM6PR11MB2890B9B211E9F5F9A78EE978BC1D0@DM6PR11MB2890.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200928044024.7595-2-mario.limonciello@dell.com>
> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
> Mario Limonciello
> Sent: Sunday, September 27, 2020 9:40 PM
> To: Kirsher, Jeffrey T <jeffrey.t.kirsher@intel.com>; intel-wired-
> lan@lists.osuosl.org
> Cc: Perry.Yuan@dell.com; Yijun.Shen@dell.com; linux-kernel@vger.kernel.org;
> Mario Limonciello <mario.limonciello@dell.com>
> Subject: [Intel-wired-lan] [PATCH 1/3] e1000e: allow turning s0ix flows on for
> systems with ME
>
> S0ix for GBE flows are needed for allowing the system to get into deepest
> power state, but these require coordination of components outside of
> control of Linux kernel. For systems that have confirmed to coordinate
> this properly, allow turning on the s0ix flows at load time or runtime.
>
> Fixes: e086ba2fccda ("e1000e: disable s0ix entry and exit flows for ME systems")
> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
> ---
> .../device_drivers/ethernet/intel/e1000e.rst | 23 ++++
> drivers/net/ethernet/intel/e1000e/e1000.h | 7 ++
> drivers/net/ethernet/intel/e1000e/netdev.c | 64 +++++-----
> drivers/net/ethernet/intel/e1000e/param.c | 110 ++++++++++++++++++
> 4 files changed, 166 insertions(+), 38 deletions(-)
>
Tested-by: Aaron Brown <aaron.f.brown@intel.com>
next prev parent reply other threads:[~2020-10-22 19:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 4:40 [PATCH 0/3] Improve s0ix flows for systems i219LM Mario Limonciello
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 ` Brown, Aaron F [this message]
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=DM6PR11MB2890B9B211E9F5F9A78EE978BC1D0@DM6PR11MB2890.namprd11.prod.outlook.com \
--to=aaron.f.brown@intel.com \
--cc=Perry.Yuan@dell.com \
--cc=Yijun.Shen@dell.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@dell.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).