From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Frans Pop <elendil@planet.nl>
Cc: oliver@neukum.org, stern@rowland.harvard.edu, 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
Subject: Re: [Regression] USB wakeup problem on Toshiba Portege R500
Date: Thu, 8 Jan 2009 20:54:44 +0100 [thread overview]
Message-ID: <200901082054.45051.rjw@sisk.pl> (raw)
In-Reply-To: <200901081955.12021.elendil@planet.nl>
On Thursday 08 January 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
One more case (a real-life example actually):
- There is a USB wireless mouse attached to the box while suspending and the
mouse is powered off by pressing a button on it. The mouse's radio receiver
remains in a USB port on the box. Now, if the mouse is powered off again,
the box will resume. What if that happens accidentally while the box is
being carried in a backpack?
> 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 have to say I agree.
Thanks,
Rafael
next prev parent reply other threads:[~2009-01-08 19:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 7:35 Rafael J. Wysocki
2009-01-08 8:49 ` Oliver Neukum
2009-01-08 16:36 ` Rafael J. Wysocki
2009-01-08 16:48 ` Oliver Neukum
2009-01-08 17:03 ` Rafael J. Wysocki
2009-01-08 18:55 ` Frans Pop
2009-01-08 19:54 ` Rafael J. Wysocki [this message]
2009-01-09 15:55 ` Alan Stern
2009-01-09 17:53 ` 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
2009-01-09 10:18 ` Pavel Machek
2009-01-09 10:26 ` Oliver Neukum
2009-01-09 10:36 ` Pavel Machek
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=200901082054.45051.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=elendil@planet.nl \
--cc=gregkh@suse.de \
--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
all inboxes | Powered by JetHome®