From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: USB list <linux-usb@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Update the policy on default wakeup settings
Date: Mon, 26 Sep 2011 17:48:29 +0200 [thread overview]
Message-ID: <201109261748.29952.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1109261120350.1918-100000@iolanthe.rowland.org>
On Monday, September 26, 2011, Alan Stern wrote:
> This patch (as1485) documents a change to the kernel's default wakeup
> policy. Devices that forward wakeup requests between buses should be
> enabled for wakeup by default.
>
> Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Applied to linux-pm/linux-next.
Thanks,
Rafael
> ---
>
> Because of the unavailability of the linux-pm mailing list, I'm posting
> this on LKML.
>
>
> Documentation/power/devices.txt | 4 +++-
> drivers/base/power/wakeup.c | 4 +++-
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> Index: usb-3.1/Documentation/power/devices.txt
> ===================================================================
> --- usb-3.1.orig/Documentation/power/devices.txt
> +++ usb-3.1/Documentation/power/devices.txt
> @@ -152,7 +152,9 @@ try to use its wakeup mechanism. device
> for the most part drivers should not change its value. The initial value of
> should_wakeup is supposed to be false for the majority of devices; the major
> exceptions are power buttons, keyboards, and Ethernet adapters whose WoL
> -(wake-on-LAN) feature has been set up with ethtool.
> +(wake-on-LAN) feature has been set up with ethtool. It should also default
> +to true for devices that don't generate wakeup requests on their own but merely
> +forward wakeup requests from one bus to another (like PCI bridges).
>
> Whether or not a device is capable of issuing wakeup events is a hardware
> matter, and the kernel is responsible for keeping track of it. By contrast,
> Index: usb-3.1/drivers/base/power/wakeup.c
> ===================================================================
> --- usb-3.1.orig/drivers/base/power/wakeup.c
> +++ usb-3.1/drivers/base/power/wakeup.c
> @@ -276,7 +276,9 @@ EXPORT_SYMBOL_GPL(device_set_wakeup_capa
> *
> * By default, most devices should leave wakeup disabled. The exceptions are
> * devices that everyone expects to be wakeup sources: keyboards, power buttons,
> - * possibly network interfaces, etc.
> + * possibly network interfaces, etc. Also, devices that don't generate their
> + * own wakeup requests but merely forward requests from one bus to another
> + * (like PCI bridges) should have wakeup enabled by default.
> */
> int device_init_wakeup(struct device *dev, bool enable)
> {
>
>
>
prev parent reply other threads:[~2011-09-26 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 15:22 Alan Stern
2011-09-26 15:48 ` Rafael J. Wysocki [this message]
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=201109261748.29952.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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
all inboxes | Powered by JetHome®