Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: 8AtsTZcyYNEjZdsGices1gIEJBEV+pwm/3PwHVwG12TFm3gYs2VtdVzNU7eRziC08Qpg+fdMXx
 5slXKFiPTqsg==
IronPort-SDR: zqrZDTpcBY429/48iEvx829mVfItS5dLAJ+RZ+qfqbrJX8xmkv7rTiKJIz8IxntzwfwT4ijMCp
 nens/ksfw/og==
From:   Chen Yu <yu.c.chen@intel.com>
To:     Jesse Brandeburg <jesse.brandeburg@intel.com>,
        Tony Nguyen <anthony.l.nguyen@intel.com>,
        Jakub Kicinski <kuba@kernel.org>,
        Kai-Heng Feng <kai.heng.feng@canonical.com>,
        Paul Menzel <pmenzel@molgen.mpg.de>
Cc:     "David S. Miller" <davem@davemloft.net>,
        "Rafael J. Wysocki" <rjw@rjwysocki.net>,
        Len Brown <len.brown@intel.com>,
        "Neftin, Sasha" <sasha.neftin@intel.com>,
        "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
        intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org,
        "Brandt, Todd E" <todd.e.brandt@intel.com>,
        Chen Yu <yu.c.chen@intel.com>
Subject: [PATCH 0/2][v3] Put the NIC in runtime suspended during s2ram
Date:   Tue,  1 Dec 2020 09:21:14 +0800
Message-Id: <cover.1606757180.git.yu.c.chen@intel.com>
Precedence: bulk

The NIC is put in runtime suspend status when there is no cable connected.
As a result, it is safe to keep non-wakeup NIC in runtime suspended during
s2ram because the system does not rely on the NIC plug event nor WoL to wake
up the system. Besides that, unlike the s2idle, s2ram does not need to
manipulate S0ix settings during suspend.

Chen Yu (2):
  e1000e: Leverage direct_complete to speed up s2ram
  e1000e: Remove the runtime suspend restriction on CNP+

 drivers/net/ethernet/intel/e1000e/netdev.c | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

-- 
2.17.1