public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Konstantin Khlebnikov <khlebnikov@openvz.org>
Cc: linux-kernel@vger.kernel.org, e1000-devel@lists.sourceforge.net,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Bruce Allan <bruce.w.allan@intel.com>
Subject: Re: [PATCH  RESEND 2/3] e1000e: fix runtime power management transitions
Date: Mon, 04 Mar 2013 17:34:48 -0800	[thread overview]
Message-ID: <1362447288.2183.4.camel@jtkirshe-mobl> (raw)
In-Reply-To: <20130225051907.12689.44621.stgit@zurg>

[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]

On Mon, 2013-02-25 at 09:19 +0400, Konstantin Khlebnikov wrote:
> This patch removes redundant actions from driver and fixes its
> interaction
> with actions in pci-bus runtime power management code.
> 
> It removes pci_save_state() from __e1000_shutdown() for normal
> adapters,
> PCI bus callbacks pci_pm_*() will do all this for us. Now
> __e1000_shutdown()
> switches to D3-state only quad-port adapters, because they needs quirk
> for
> clearing false-positive error from downsteam pci-e port.
> 
> pci_save_state() now called after clearing bus-master bit, thus
> __e1000_resume()
> and e1000_io_slot_reset() must set it back after restoring
> configuration space.
> 
> This patch set get_link_status before calling pm_runtime_put() in
> e1000_open()
> to allow e1000_idle() get real link status and schedule first runtime
> suspend.
> 
> This patch also enables wakeup for device if management mode is
> enabled
> (like for WoL) as result pci_prepare_to_sleep() would setup wakeup
> without
> special actions like custom 'enable_wakeup' sign.
> 
> Signed-off-by: Konstantin Khlebnikov <khlebnikov@openvz.org>
> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Cc: e1000-devel@lists.sourceforge.net
> Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Cc: Bruce Allan <bruce.w.allan@intel.com>
> ---
>  drivers/net/ethernet/intel/e1000e/netdev.c |   78
> ++++++----------------------
>  1 file changed, 18 insertions(+), 60 deletions(-) 

I have added this patch to my e1000e patch queue.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-03-05  1:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25  5:18 [PATCH RESEND 0/3] e1000e: return runtime-pm back to work Konstantin Khlebnikov
2013-02-25  5:19 ` [PATCH RESEND 1/3] e1000e: fix pci-device enable-counter balance Konstantin Khlebnikov
2013-03-05  1:33   ` Jeff Kirsher
2013-02-25  5:19 ` [PATCH RESEND 2/3] e1000e: fix runtime power management transitions Konstantin Khlebnikov
2013-03-05  1:34   ` Jeff Kirsher [this message]
2013-02-25  5:19 ` [PATCH RESEND 3/3] e1000e: fix accessing to suspended device Konstantin Khlebnikov
2013-02-26  1:09   ` [E1000-devel] " Waskiewicz Jr, Peter P
2013-02-26 10:03     ` Konstantin Khlebnikov
2013-02-26 23:35       ` Ben Hutchings
2013-03-02 12:26         ` Konstantin Khlebnikov
2013-03-05  1:35   ` Jeff Kirsher

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=1362447288.2183.4.camel@jtkirshe-mobl \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=bruce.w.allan@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=khlebnikov@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@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