All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Wakeup and S states
Date: Thu, 16 Jun 2011 10:32:29 -0400	[thread overview]
Message-ID: <4DFA13FD.6020304@cfl.rr.com> (raw)
In-Reply-To: <20110616141517.GB15242@srcf.ucam.org>

On 6/16/2011 10:15 AM, Matthew Garrett wrote:
> Yes. How would the kernel know that you don't want WoL in that case?

That was my original point; the kernel architecture seems lacking since 
it does not consider what S state you are talking about wrt wakeup 
capability and policy.  I can see the argument that policy should be 
dynamically changed in user space, but it seems that the kernel really 
needs to track the capability as it relates to S state so you don't try 
to enable wakeup in states where it is not possible.

  reply	other threads:[~2011-06-16 14:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15 15:12 Wakeup and S states Phillip Susi
2011-06-15 15:44 ` Matthew Garrett
2011-06-16 13:48   ` Phillip Susi
2011-06-16 14:15     ` Matthew Garrett
2011-06-16 14:32       ` Phillip Susi [this message]
2011-06-16 14:37         ` Matthew Garrett
2011-06-16 15:11           ` Phillip Susi

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=4DFA13FD.6020304@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    /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.