From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Shaohua Li <shaohua.li@intel.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: USB runtime D3
Date: Thu, 30 Jul 2009 03:56:57 +0100 [thread overview]
Message-ID: <20090730025657.GE26389@srcf.ucam.org> (raw)
In-Reply-To: <20090730023313.GA27493@sli10-desk.sh.intel.com>
On Thu, Jul 30, 2009 at 10:33:13AM +0800, Shaohua Li wrote:
> There are patches to support both ACPI based wakeup event and PCIe native
> wakeup event in below bugzilla, but it never gets into upstream. One problem
> is how to check which device under a bridge generates a wakeup event, because
> pci devices can share a wakeup event.
> There are discussion in pm list about the patches too, please search.
Yes, that would basically work for me. I'm still slightly curious as to
why my hardware's not giving me the correct ACPI notification, though -
I guess this may be entirely untested under Windows.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-07-30 2:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 2:06 USB runtime D3 Matthew Garrett
[not found] ` <20090730020623.GB26389-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-07-30 2:33 ` Shaohua Li
2009-07-30 2:56 ` Matthew Garrett [this message]
2009-07-30 3:17 ` Shaohua Li
2009-07-30 3:18 ` Matthew Garrett
2009-07-30 18:58 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0907301458090.6087-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2009-07-30 19:02 ` Matthew Garrett
[not found] ` <20090730190243.GA22016-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-07-30 19:15 ` Alan Stern
2009-07-30 19:23 ` Matthew Garrett
2009-07-30 18:57 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0907301447080.6087-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2009-07-30 19:07 ` Matthew Garrett
2009-07-30 19:22 ` Alan Stern
2009-07-30 19:26 ` 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=20090730025657.GE26389@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shaohua.li@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