From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: "Yan, Zheng" <zheng.z.yan@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
e1000-devel@lists.sourceforge.net,
"davem@davemloft.net" <davem@davemloft.net>,
jesse.brandeburg@intel.com, bruce.w.allan@intel.com,
carolyn.wyborny@intel.com, donald.c.skidmore@intel.com,
gregory.v.rose@intel.com, peter.p.waskiewicz.jr@intel.com,
alexander.h.duyck@intel.com, john.ronciak@intel.com, rjw@sisk.pl
Subject: Re: [PATCH net-next V2] igb: add basic runtime PM support
Date: Wed, 21 Dec 2011 16:57:20 -0800 [thread overview]
Message-ID: <1324515440.2327.25.camel@jtkirshe-mobl> (raw)
In-Reply-To: <4EF16CC2.80806@intel.com>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
On Wed, 2011-12-21 at 13:21 +0800, Yan, Zheng wrote:
> Use the runtime power management framework to add basic runtime PM
> support
> to the igb driver. Namely, make the driver suspend the device when the
> link
> is off and set it up for generating a wakeup event after the link has
> been
> detected again. This feature is disabled by default.
>
> Based on e1000e's runtime PM code.
>
> Signed-off-by: Zheng Yan <zheng.z.yan@intel.com>
> ---
> Changes since v1:
> Don't suspend the device when shutting down the interface.
> Avoid race between runtime suspending and ethtool operations.
>
> drivers/net/ethernet/intel/igb/igb_ethtool.c | 16 +++
> drivers/net/ethernet/intel/igb/igb_main.c | 136
> ++++++++++++++++++++++----
> 2 files changed, 133 insertions(+), 19 deletions(-)
I have applied this to my queue of patches. Thanks Zheng!
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-12-22 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 5:21 [PATCH net-next V2] igb: add basic runtime PM support Yan, Zheng
2011-12-22 0:57 ` Jeff Kirsher [this message]
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=1324515440.2327.25.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=davem@davemloft.net \
--cc=donald.c.skidmore@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gregory.v.rose@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=rjw@sisk.pl \
--cc=zheng.z.yan@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).