[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DM6PR11MB2890B9B211E9F5F9A78EE978BC1D0@DM6PR11MB2890.namprd11.prod.outlook.com>
Date: Thu, 22 Oct 2020 19:21:04 +0000
From: "Brown, Aaron F" <aaron.f.brown@...el.com>
To: Mario Limonciello <mario.limonciello@...l.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
CC: "Perry.Yuan@...l.com" <Perry.Yuan@...l.com>,
"Yijun.Shen@...l.com" <Yijun.Shen@...l.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [Intel-wired-lan] [PATCH 1/3] e1000e: allow turning s0ix flows on
for systems with ME
> From: Intel-wired-lan <intel-wired-lan-bounces@...osl.org> On Behalf Of
> Mario Limonciello
> Sent: Sunday, September 27, 2020 9:40 PM
> To: Kirsher, Jeffrey T <jeffrey.t.kirsher@...el.com>; intel-wired-
> lan@...ts.osuosl.org
> Cc: Perry.Yuan@...l.com; Yijun.Shen@...l.com; linux-kernel@...r.kernel.org;
> Mario Limonciello <mario.limonciello@...l.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@...l.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@...el.com>
Powered by blists - more mailing lists