From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Frans Pop <elendil@planet.nl>,
oliver@neukum.org, gregkh@suse.de, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org, pavel@suse.cz,
torvalds@linux-foundation.org,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [Regression] USB wakeup problem on Toshiba Portege R500
Date: Tue, 13 Jan 2009 12:13:25 +0100 [thread overview]
Message-ID: <200901131213.26836.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0901122207400.18052-100000@netrider.rowland.org>
On Tuesday 13 January 2009, Alan Stern wrote:
> On Mon, 12 Jan 2009, Rafael J. Wysocki wrote:
>
> > On Monday 12 January 2009, Alan Stern wrote:
> > > On Fri, 9 Jan 2009, Rafael J. Wysocki wrote:
> > >
> > > > > My proposal:
> > > > >
> > > > > Devices and events that are clearly associated with system
> > > > > wakeup should be enabled by default. For example: Power
> > > > > button and laptop lid.
> > > >
> > > > Agreed.
> > > >
> > > > > All other devices capable of waking up the system should be
> > > > > disabled by default. This presumably includes every PCI
> > > > > device. If users want keyboard or mouse events to cause
> > > > > a system resume then they will have to configure their
> > > > > desktop management program to enable it.
> > > >
> > > > I generally agree, with one exception. There are network adapters which
> > > > can be enabled to wake up by the BIOS and their drivers set them up for WoL
> > > > currently on this basis. These should remain enabled IMO.
> > >
> > > How do we know which adapters these are? IMO the PCI core should
> > > disable wakeup by default for all devices when they are detected.
> >
> > This is what we do.
> >
> > > Is it sufficient to have the adapter drivers enable wakeup during
> > > their probe routines?
> >
> > Yes, it is.
>
> Therefore all we need is a patch to change the USB host controller
> drivers. They should call device_set_wakeup_capable() instead of
> device_init_wakeup().
>
> I just got back from vacation so things will be busy for a few days,
> but I'll send out such a patch soon.
Great, thanks a lot!
Rafael
prev parent reply other threads:[~2009-01-13 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.0901091055050.10951-100000@netrider.rowland.org>
2009-01-09 17:53 ` [Regression] USB wakeup problem on Toshiba Portege R500 Rafael J. Wysocki
2009-01-09 22:23 ` Pavel Machek
2009-01-12 21:53 ` Alan Stern
2009-01-12 22:53 ` Rafael J. Wysocki
2009-01-13 3:10 ` Alan Stern
2009-01-13 11:13 ` 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=200901131213.26836.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=elendil@planet.nl \
--cc=gregkh@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=oliver@neukum.org \
--cc=pavel@suse.cz \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox