public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux acpi <linux-acpi@vger.kernel.org>,
	pm list <linux-pm@lists.linux-foundation.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH 1/5] introduce .wakeup_event ops
Date: Fri, 21 Aug 2009 14:33:50 +0800	[thread overview]
Message-ID: <20090821063350.GA16694@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20090820074050.GA30288@srcf.ucam.org>

On Thu, Aug 20, 2009 at 03:40:51PM +0800, Matthew Garrett wrote:
> On Thu, Aug 20, 2009 at 11:24:50AM +0800, Shaohua Li wrote:
> > On Wed, Aug 19, 2009 at 07:52:10PM +0800, Matthew Garrett wrote:
> > > I'm not averse to the general concept, but I'm not entirely sold on it 
> > > being necessary. All the hardware I'm aware of will send non-PME events 
> > > as a notification on a specific device. Under what circumstances will we 
> > > get a wakeup GPE for a non-PME device without knowing which device 
> > > should be woken?
> > Below code is gotten from a laptop (samsung-x10), the PCIB is the PCI bridge.
> > We can't guarantee the device which gets a wakeup event notification is really
> > the device which invokes the wakeup event.
> 
> _L0B will only be triggered if a PME is generated, so we'll be able to 
> determine which device generated the wakeup by looking at the PME 
> registers.
Right, but the event is sent to a bridge. The devices under the bridge invoke
wakeup event, not the bridge itself. So you must scan all devices under the
bridge to check which device has its PME registers set.
So the bridge case isn't what you said (notification always sent to a specific
device which invokes the wakeup event)

Thanks,
Shaohua

  reply	other threads:[~2009-08-21  6:33 UTC|newest]

Thread overview: 21+ 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-20  3:24   ` Shaohua Li
2009-08-20  7:40     ` Matthew Garrett
2009-08-21  6:33       ` Shaohua Li [this message]
2009-08-21  9:23         ` Matthew Garrett
2009-08-24  1:50           ` Shaohua Li
2009-08-24  2:48             ` 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-19 14:49 ` Alan Stern
2009-08-20  3:04   ` Shaohua Li
2009-08-20 14:11     ` Alan Stern
2009-08-20 14:14       ` Matthew Garrett
2009-08-20 14:38         ` Alan Stern
2009-08-20 14:42           ` Matthew Garrett
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:27                   ` Rafael J. Wysocki
2009-08-21  6:46                     ` Shaohua Li
2009-08-21 14:33                       ` Alan Stern

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=20090821063350.GA16694@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mjg59@srcf.ucam.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