From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH] PCI / PM: Disable wakeup during shutdown for devices not enabled to wake up
Date: Fri, 10 Feb 2012 15:51:45 -0800 [thread overview]
Message-ID: <20120210155145.74aafa88@jbarnes-desktop> (raw)
In-Reply-To: <201202102340.29644.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 2898 bytes --]
On Fri, 10 Feb 2012 23:40:29 +0100
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> On Friday, February 10, 2012, Jesse Barnes wrote:
> > On Tue, 7 Feb 2012 00:50:35 +0100
> > "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> >
> > > From: Rafael J. Wysocki <rjw@sisk.pl>
> > >
> > > If a PCI device is enabled to generate wakeup signals (PME) when put
> > > into a low-power state by runtime PM, it will be still enabled to
> > > generate those signals after the system shutdown, unless its driver's
> > > .shutdown() callback takes care of the wakeup signals generation
> > > setting. Moreover, there are devices that are not enabled to wake
> > > up the system and that are configured by runtime PM to generate
> > > wakeup signals so that (runtime) remote wakeup works with them.
> > > Those devices should be reconfigured during system shutdown so that
> > > they don't generate wakeup signals, but at least some drivers don't
> > > do that. However, that very well may be done by the PCI core so
> > > that drivers don't have to worry about it. For this reason, modify
> > > pci_device_shutdown() to disable the generation of wakeup events for
> > > devices not supposed to wake up the system.
> > >
> > > References: https://bugzilla.kernel.org/show_bug.cgi?id=37952
> > > Reported-and-tested-by: Kamil Iskra <kamil.54002@iskra.name>
> > > Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> > > ---
> > > drivers/pci/pci-driver.c | 10 ++++++++++
> > > 1 file changed, 10 insertions(+)
> > >
> > > Index: linux/drivers/pci/pci-driver.c
> > > ===================================================================
> > > --- linux.orig/drivers/pci/pci-driver.c
> > > +++ linux/drivers/pci/pci-driver.c
> > > @@ -430,6 +430,16 @@ static void pci_device_shutdown(struct d
> > > drv->shutdown(pci_dev);
> > > pci_msi_shutdown(pci_dev);
> > > pci_msix_shutdown(pci_dev);
> > > +
> > > + /*
> > > + * Devices may be enabled to wake up by runtime PM, but they need not
> > > + * be supposed to wake up the system from its "power off" state (e.g.
> > > + * ACPI S5). Therefore disable wakeup for all devices that aren't
> > > + * supposed to wake up the system at this point. The state argument
> > > + * will be ignored by pci_enable_wake().
> > > + */
> > > + if (!device_may_wakeup(dev))
> > > + pci_enable_wake(pci_dev, PCI_UNKNOWN, false);
> > > }
> > >
> > > #ifdef CONFIG_PM
> > >
> >
> > So where do we end up setting the right wakeup state for devices we
> > actually *do* want to wake the system from S5? Presumably later in the
> > shutdown sequence?
>
> Yes, in general. However, device_may_wakeup(dev) has to return true for those
> devices, so they aren't affected by this change.
Ok thanks Rafael, applied. Now to do a little testing...
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-10 23:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 23:50 [PATCH] PCI / PM: Disable wakeup during shutdown for devices not enabled to wake up Rafael J. Wysocki
2012-02-10 20:34 ` Jesse Barnes
2012-02-10 22:40 ` Rafael J. Wysocki
2012-02-10 23:51 ` Jesse Barnes [this message]
2012-03-02 14:44 ` Francois Romieu
2012-03-02 17:37 ` Jesse Barnes
2012-03-02 18:04 ` Jesse Barnes
2012-03-02 18:08 ` Alan Stern
2012-03-02 20:49 ` Rafael J. Wysocki
2012-03-02 20:57 ` Rafael J. Wysocki
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=20120210155145.74aafa88@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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).