From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-pm@lists.linux-foundation.org
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Linux PCI <linux-pci@vger.kernel.org>
Subject: [RFC][PATCH 0/4] PCI/ACPI PM: Propagate wake-up enable upstream
Date: Fri, 4 Sep 2009 00:02:02 +0200 [thread overview]
Message-ID: <200909040002.02562.rjw@sisk.pl> (raw)
In-Reply-To: <200909020041.57754.rjw@sisk.pl>
On Wednesday 02 September 2009, Rafael J. Wysocki wrote:
> On Tuesday 01 September 2009, Rafael J. Wysocki wrote:
> > On Tuesday 01 September 2009, Matthew Garrett wrote:
> > > On Mon, Aug 31, 2009 at 11:24:20PM +0200, Rafael J. Wysocki wrote:
> > >
> > > > Updated patch is appended, but there's a problem with it. Namely, when the
> > > > root bridge GPE is shared with other devices, those devices are also enabled
> > > > to wake up and they may be kind of "interesting" (on one of my test boxes they
> > > > include the ethernet and audio adapters). I'm not sure what to do about that.
> > >
> > > Perhaps only enable it if a child device is enabled?
> >
> > Well, the problem is that we have to enable the devices that share the GPE to
> > wake up together, but the child device we _really_ want to wake-up need not
> > be any of them.
> >
> > Also, the child device may be enabled to wake up after we've run the "glue"
> > code.
> >
> > Well, perhaps it's better to rework pci_enable_wake() so that it, if the device
> > doesn't have an ACPI handle and is not PCIe, it will go and enable the root
> > bridge to wake up as well?
> >
> > I wonder what about the bridges between the desired wake-up device and the
> > root bridge. I guess they also should be enabled to wake-up, so that they can
> > forward the PME# in case the system is designed this way.
>
> Below is a prototype of what I was thinking of, although I'm not sure if that's
> enough.
>
> Comments welcome.
Hm, no comments. :-(
In the meantime I spent some time on this problem and prepared the following
series of patches.
The last one has to be tested on the system it was invented for, but that's
going to take some time.
Comments welcome.
Rafael
next prev parent reply other threads:[~2009-09-03 22:06 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 22:41 [PATCH] ACPI / PM: Allow PCI root bridges to wake up the system Rafael J. Wysocki
2009-08-31 19:41 ` Rafael J. Wysocki
2009-08-31 19:41 ` [linux-pm] " Rafael J. Wysocki
2009-08-31 21:24 ` [RFC][PATCH update] " Rafael J. Wysocki
2009-08-31 21:24 ` Rafael J. Wysocki
2009-09-01 13:25 ` Matthew Garrett
2009-09-01 19:03 ` Rafael J. Wysocki
2009-09-01 22:41 ` Rafael J. Wysocki
2009-09-01 22:41 ` [linux-pm] " Rafael J. Wysocki
2009-09-03 22:02 ` [RFC][PATCH 0/4] PCI/ACPI PM: Propagate wake-up enable upstream Rafael J. Wysocki
2009-09-03 22:02 ` Rafael J. Wysocki [this message]
2009-09-03 22:03 ` [RFC][PATCH 1/4] PCI PM: Simplify PCI wake-up code Rafael J. Wysocki
2009-09-03 22:03 ` Rafael J. Wysocki
2009-09-03 22:04 ` [RFC][PATCH 2/4] PCI/ACPI PM: Rework some debug messages Rafael J. Wysocki
2009-09-03 22:04 ` Rafael J. Wysocki
2009-09-03 22:05 ` [RFC][PATCH 3/4] PCI PM: Introduce device flag wakeup_prepared Rafael J. Wysocki
2009-09-03 22:05 ` Rafael J. Wysocki
2009-09-03 22:07 ` [RFC][PATCH 4/4] PCI/ACPI PM: Propagate wake-up enable for devices w/o ACPI support Rafael J. Wysocki
2009-09-04 2:13 ` ykzhao
2009-09-04 2:13 ` ykzhao
2009-09-04 14:39 ` Rafael J. Wysocki
2009-09-04 14:56 ` Matthew Garrett
2009-09-04 22:00 ` Rafael J. Wysocki
2009-09-04 22:00 ` Rafael J. Wysocki
2009-09-04 22:06 ` Matthew Garrett
2009-09-04 22:06 ` Matthew Garrett
2009-09-04 22:21 ` Rafael J. Wysocki
2009-09-04 22:21 ` Rafael J. Wysocki
2009-09-04 14:56 ` Matthew Garrett
2009-09-04 14:39 ` Rafael J. Wysocki
2009-09-04 22:03 ` Rafael J. Wysocki
2009-09-04 22:03 ` [linux-pm] " Rafael J. Wysocki
2009-09-04 22:05 ` [RFC][PATCH 4/4 replacement] ACPI PM: Replace wakeup.prepared with reference counter Rafael J. Wysocki
2009-09-04 22:05 ` Rafael J. Wysocki
2009-09-04 22:06 ` [RFC][PATCH 5] PCI/ACPI PM: Propagate wake-up enable for devices w/o ACPI support Rafael J. Wysocki
2009-09-04 22:06 ` Rafael J. Wysocki
2009-09-03 22:07 ` [RFC][PATCH 4/4] " Rafael J. Wysocki
2009-09-08 21:11 ` [PATCH 0/5 update] PCI / ACPI PM: Propagate wake-up enable upstream Rafael J. Wysocki
2009-09-08 21:12 ` [PATCH 1/5] PCI PM: Simplify PCI wake-up code Rafael J. Wysocki
2009-09-08 21:12 ` Rafael J. Wysocki
2009-09-09 21:20 ` Jesse Barnes
2009-09-09 21:20 ` Jesse Barnes
2009-09-08 21:13 ` [PATCH 2/5] PCI / ACPI PM: Rework some debug messages Rafael J. Wysocki
2009-09-08 21:13 ` Rafael J. Wysocki
2009-09-08 21:14 ` [PATCH 3/5] PCI PM: Introduce device flag wakeup_prepared Rafael J. Wysocki
2009-09-08 21:14 ` Rafael J. Wysocki
2009-09-08 21:15 ` [PATCH 4/5] ACPI PM: Replace wakeup.prepared with reference counter Rafael J. Wysocki
2009-09-08 21:15 ` Rafael J. Wysocki
2009-09-08 21:16 ` [PATCH 5/5] PCI / ACPI PM: Propagate wake-up enable for devices w/o ACPI support Rafael J. Wysocki
2009-09-08 21:16 ` Rafael J. Wysocki
2009-09-08 21:11 ` [PATCH 0/5 update] PCI / ACPI PM: Propagate wake-up enable upstream Rafael J. Wysocki
2009-09-01 19:03 ` [RFC][PATCH update] ACPI / PM: Allow PCI root bridges to wake up the system Rafael J. Wysocki
2009-09-01 13:25 ` Matthew Garrett
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=200909040002.02562.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=hmh@hmh.eng.br \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.