[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <309B89C4C689E141A5FF6A0C5FB2118B9660FBCD@ORSMSX103.amr.corp.intel.com>
Date: Sat, 5 Jan 2019 04:04:24 +0000
From: "Brown, Aaron F" <aaron.f.brown@...el.com>
To: Kai-Heng Feng <kai.heng.feng@...onical.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/2] e1000e: Exclude device from suspend direct complete
optimization
> From: netdev-owner@...r.kernel.org [mailto:netdev-
> owner@...r.kernel.org] On Behalf Of Kai-Heng Feng
> Sent: Tuesday, December 11, 2018 12:00 AM
> To: Kirsher, Jeffrey T <jeffrey.t.kirsher@...el.com>
> Cc: davem@...emloft.net; intel-wired-lan@...ts.osuosl.org;
> netdev@...r.kernel.org; linux-kernel@...r.kernel.org; Kai-Heng Feng
> <kai.heng.feng@...onical.com>
> Subject: [PATCH 1/2] e1000e: Exclude device from suspend direct complete
> optimization
>
> e1000e sets different WoL settings in system suspend callback and
> runtime suspend callback.
>
> The suspend direct complete optimization leaves e1000e in runtime
> suspneded state with wrong WoL setting during system suspend.
>
> To fix this, we need to disable suspend direct complete optimization to
> let e1000e always use suspend callback to set correct WoL during system
> suspend.
>
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@...onical.com>
> ---
> drivers/net/ethernet/intel/e1000e/netdev.c | 2 ++
> 1 file changed, 2 insertions(+)
>
Tested-by: Aaron Brown <aaron.f.brown@...el.com>
Powered by blists - more mailing lists