From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Shaohua Li <shaohua.li@intel.com>,
linux acpi <linux-acpi@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH 1/5] introduce .wakeup_event ops
Date: Thu, 20 Aug 2009 15:14:36 +0100 [thread overview]
Message-ID: <20090820141436.GA3722@srcf.ucam.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0908201004100.3048-100000@iolanthe.rowland.org>
On Thu, Aug 20, 2009 at 10:11:19AM -0400, Alan Stern wrote:
> How is the wakeup event received? Maybe for this one type of device a
> PCI quirk will solve the problem.
Pretty much the same as PME events on PCI - a GPE is generated, an SCI
raised, the ACPI interpreter executes the code that's in the ACPI
tables, that generates a notification event on the appropriate UHCI
device, we live happily ever after.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-08-20 14:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 7:24 [PATCH 1/5] introduce .wakeup_event ops Shaohua Li
2009-08-19 11:52 ` Matthew Garrett
2009-08-19 11:52 ` Matthew Garrett
2009-08-20 3:24 ` Shaohua Li
2009-08-20 3:24 ` Shaohua Li
2009-08-20 7:40 ` Matthew Garrett
2009-08-21 6:33 ` Shaohua Li
2009-08-21 9:23 ` Matthew Garrett
2009-08-21 9:23 ` Matthew Garrett
2009-08-24 1:50 ` Shaohua Li
2009-08-24 2:48 ` Matthew Garrett
2009-08-24 2:48 ` Matthew Garrett
2009-08-24 1:50 ` Shaohua Li
2009-08-21 6:33 ` Shaohua Li
2009-08-20 7:40 ` Matthew Garrett
[not found] ` <20090824082722.GA32264@srcf.ucam.org>
[not found] ` <1251103572.24336.8.camel@sli10-desk.sh.intel.com>
2009-08-24 18:49 ` Rafael J. Wysocki
2009-08-24 18:49 ` Rafael J. Wysocki
2009-08-19 14:49 ` Alan Stern
2009-08-20 3:04 ` Shaohua Li
2009-08-20 14:11 ` Alan Stern
2009-08-20 14:11 ` Alan Stern
2009-08-20 14:14 ` Matthew Garrett [this message]
2009-08-20 14:38 ` Alan Stern
2009-08-20 14:38 ` Alan Stern
2009-08-20 14:42 ` Matthew Garrett
2009-08-20 15:22 ` Alan Stern
2009-08-20 15:22 ` Alan Stern
2009-08-20 19:37 ` Rafael J. Wysocki
2009-08-20 21:10 ` Alan Stern
2009-08-20 21:10 ` Alan Stern
2009-08-20 21:27 ` Rafael J. Wysocki
2009-08-21 6:46 ` Shaohua Li
2009-08-21 6:46 ` Shaohua Li
2009-08-21 14:33 ` Alan Stern
2009-08-21 14:33 ` Alan Stern
2009-08-20 21:27 ` Rafael J. Wysocki
2009-08-20 19:37 ` Rafael J. Wysocki
2009-08-20 14:42 ` Matthew Garrett
2009-08-20 14:14 ` Matthew Garrett
2009-08-20 3:04 ` Shaohua Li
2009-08-19 14:49 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2009-08-19 7:24 Shaohua Li
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=20090820141436.GA3722@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=shaohua.li@intel.com \
--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 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.