public inbox for linux-pm@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>,
	linux-pm <linux-pm@lists.osdl.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH 5/5] acpi-based wakeup event detection
Date: Thu, 20 Aug 2009 11:16:51 +0800	[thread overview]
Message-ID: <20090820031651.GC26357@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20090819114220.GA12216@srcf.ucam.org>

On Wed, Aug 19, 2009 at 07:42:20PM +0800, Matthew Garrett wrote:
> On Wed, Aug 19, 2009 at 03:24:21PM +0800, Shaohua Li wrote:
> 
> > +	ret = acpi_gpe_pme_check(dev);
> > +
> > +	acpi_disable_gpe(dev->wakeup.gpe_device, dev->wakeup.gpe_number);
> 
> I don't think we want to unconditionally disable the GPE.
yes, we need something you proposed to add reference for GPE disable/enable.
 
> > +
> > +	acpi_init_gpe_pme();
> 
> I'm also not keen on haing the notifier being at the ACPI level. Are we 
> guaranteed that the GPE will only be used for wakeups, and will never 
> trigger any other sort of notification? Keeping this at the bus level 
> may be more practical.
the notification handler checks if this is a wakeup event.
Because the ACPI wakeup event can be sent to any kind of buses, so move the
code to acpi level can reduce a lot of duplicate code, otherwise you must
implement the same mechanism for every bus.

Thanks,
Shaohua

  reply	other threads:[~2009-08-20  3:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19  7:24 [PATCH 5/5] acpi-based wakeup event detection Shaohua Li
2009-08-19 11:42 ` Matthew Garrett
2009-08-20  3:16   ` Shaohua Li [this message]
2009-08-20 20:03 ` Rafael J. Wysocki

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=20090820031651.GC26357@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.osdl.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