From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alan Stern <stern@rowland.harvard.edu>,
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,
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: Fri, 9 Jan 2009 23:23:43 +0100 [thread overview]
Message-ID: <20090109222343.GA2223@elf.ucw.cz> (raw)
In-Reply-To: <200901091853.42700.rjw@sisk.pl>
On Fri 2009-01-09 18:53:41, Rafael J. Wysocki wrote:
> [CCing ACPI and Len)
>
> On Friday 09 January 2009, Alan Stern wrote:
> > On Thu, 8 Jan 2009, Frans Pop wrote:
> >
> > > Rafael J. Wysocki wrote:
> > > > On Thursday 08 January 2009, Oliver Neukum wrote:
> > > >> Am Thursday 08 January 2009 17:36:12 schrieb Rafael J. Wysocki:
> > > >> You are making a very persuasive argument for reverting it.
> > > >> But what about laptops that only have a USB keyboard?
> > > >
> > > > Well, up to and including 2.6.28 they needed to echo 'enable' to the USB
> > > > controllers' /sys/devices/.../power/wakeup files, so if the patch is
> > > > reverted, they won't be worse off than they were day before
> > > > yesterday. :-)
> > > >
> > > > Perhaps we can choose the default depending on whether or not any HID
> > > > devices are attached to given controller?
> > >
> > > Is "resume on keyboard activity" really all that needed? Both my laptops
> > > and my desktop resume fine after pressing the power button.
> > >
> > > Also consider the following cases:
> > > - laptop has been suspended with external USB mouse connected
> > > - mouse is moved (accidentally or because it is in the way of a coffee
> > > cup)
> > > - mouse cable is removed before putting the laptop in a bag for
> > > transport
> > > - laptop is in docking station with USB mouse/kbd connected to that
> > > - again, mouse gets moved for some reason
> > > - laptop is undocked while suspended
> > > - or the reverse: laptop gets docked
> > >
> > > IMO it is not desirable that the system gets resumed as a result of any of
> > > those actions. I'm not complete sure that it would in all those cases,
> > > but have they been considered?
> > >
> > > And in general I've always been in favor of things only happening
> > > automagically if I've explicitly asked for that, and not by default.
> >
> > I don't mind reverting the "automatically enable PCI wakeup" commit. But
> > we should first come to a definite policy for kernel default wakeup
> > settings, rather than deciding things piecemeal for different subsystems.
> >
> > 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.
Agreed. WoL worked before and it should remain working.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-01-09 22:21 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 [this message]
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
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=20090109222343.GA2223@elf.ucw.cz \
--to=pavel@suse.cz \
--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=rjw@sisk.pl \
--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