public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux acpi <linux-acpi@vger.kernel.org>,
	pm list <linux-pm@lists.linux-foundation.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, mjg59 <mjg59@srcf.ucam.org>
Subject: Re: [PATCH 1/5] introduce .wakeup_event ops
Date: Thu, 20 Aug 2009 11:04:23 +0800	[thread overview]
Message-ID: <20090820030423.GA26357@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0908191044060.3001-100000@iolanthe.rowland.org>

On Wed, Aug 19, 2009 at 10:49:30PM +0800, Alan Stern wrote:
> On Wed, 19 Aug 2009, Shaohua Li wrote:
> 
> > Introduce .wakeup_event(). When a device gets a wakeup event,
> > the callback is called. The callback usually should check if the device
> > really invokes wakeup event and disable wakeup event if yes.
> > 
> > Usually driver should does nothing in the op as bus can handle it. But in some
> > cases, like pci bus, UHCI controller doesn't use standard PME registers for
> > wakeup, instead of using special approach. In this case, UHCI controller driver
> > should implement this op.
> 
> I don't understand the reason behind this.  Doesn't this sort of thing
> belong in the bus and platform code, not in the PM core?  (In the case
> of UHCI, it should be handled by the platform, in the same way as
> remote wakeup gets enabled before the suspend.)
> 
> Drivers don't have to be involved at all.  When a wakeup signal is 
> detected, the driver's runtime_resume method should get called -- 
> nothing more is needed.
The only case is UHCI in my mind. Because UHCI has non-standard wakeup event
register. If BIOS doesn't handle it correctly (for example, not clear the wakeup
event after a GPE), we will keep see the wakeup event. And the bus/platform
level has no knowledge to handle such event.

Thanks,
Shaohua

  reply	other threads:[~2009-08-20  3:04 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
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 [this message]
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=20090820030423.GA26357@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