All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Len Brown <lenb@kernel.org>,
	Huang Ying <ying.huang@intel.com>,
	Zhang Rui <rui.zhang@intel.com>,
	linux-acpi@vger.kernel.org
Subject: Re: Discussion on device's runtime wake capability
Date: Wed, 10 Oct 2012 08:55:46 +0800	[thread overview]
Message-ID: <5074C792.1030109@intel.com> (raw)
In-Reply-To: <20121009205723.GA12385@srcf.ucam.org>

On 10/10/2012 04:57 AM, Matthew Garrett wrote:
> On Tue, Oct 09, 2012 at 10:48:58PM +0200, Rafael J. Wysocki wrote:
> 
>> Why do you think so?  How can you be sure that those resources are not needed
>> to provide wakeup power to the device (or whatever generates the wakeup signal
>> on its behalf))?
> 
> Right. For instance, on some Thinkpads turning off the power resources 
> cuts power to the port entirely - there's no way to generate wakeups if 
> there's no 5V line...

Thanks for the info, and I've a question.
Are these ports run wake capable? i.e. do they have a _S0W object?

-Aaron


  reply	other threads:[~2012-10-10  0:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09  6:23 Discussion on device's runtime wake capability Aaron Lu
2012-10-09  6:39 ` Zhang, Rui
2012-10-09 14:44   ` Aaron Lu
2012-10-09 20:51     ` Rafael J. Wysocki
2012-10-09 20:50   ` Rafael J. Wysocki
2012-10-09 20:48 ` Rafael J. Wysocki
2012-10-09 20:57   ` Matthew Garrett
2012-10-10  0:55     ` Aaron Lu [this message]
2012-10-10  0:53   ` Aaron Lu
2012-10-10  7:54     ` Aaron Lu
2012-10-10 22:59     ` Rafael J. Wysocki
2012-10-11  0:47       ` Aaron Lu
2012-10-11 17:18         ` Rafael J. Wysocki
2012-10-12 14:15           ` Aaron Lu
2012-10-13 17:13             ` 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=5074C792.1030109@intel.com \
    --to=aaron.lu@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rjw@sisk.pl \
    --cc=rui.zhang@intel.com \
    --cc=ying.huang@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 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.