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 [thread overview]
Message-ID: <cover.1606757180.git.yu.c.chen@intel.com> (raw)
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
next reply other threads:[~2020-12-01 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 1:21 Chen Yu [this message]
2020-12-01 1:21 ` [PATCH 1/2][v3] e1000e: Leverage direct_complete to speed up s2ram Chen Yu
2020-12-02 13:06 ` Kai-Heng Feng
2020-12-02 15:40 ` Chen Yu
2020-12-01 1:22 ` [PATCH 2/2][v3] e1000e: Remove the runtime suspend restriction on CNP+ Chen Yu
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=cover.1606757180.git.yu.c.chen@intel.com \
--to=yu.c.chen@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=kuba@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=rjw@rjwysocki.net \
--cc=sasha.neftin@intel.com \
--cc=todd.e.brandt@intel.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).