mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Corrado Zoccolo <czoccolo@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: oliver@neukum.name, Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.6.30rc1 mouse stuck with usb autosuspend enabled
Date: Thu, 16 Apr 2009 14:45:12 +0200	[thread overview]
Message-ID: <4e5e476b0904160545h1f384dbdx4161a0a304ad4c80@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.00.0904161210450.10907@twin.jikos.cz>

On Thu, Apr 16, 2009 at 12:15 PM, Jiri Kosina <jkosina@suse.cz> wrote:
>
> [ added Oliver to CC ]
>
> On Thu, 9 Apr 2009, Corrado Zoccolo wrote:
>
>> I found this regression w.r.t. 2.6.29.
>> When enabling usb automatic power management for all usb peripherals, with:
>> > for i in /sys/bus/usb/devices/*/power/level; do echo auto > $i; done
>
> Well, it's difficult to consider this to be a regression. With default
> settings (USB autosuspend turned off), the system behaves the same way as
> it did before (ie. no mouse autosuspend).
>
>> after 2 seconds of inactivity (my autosuspend threshold), the mouse
>> gets stuck under X.
>
> That's because it got suspended, as you have configured it to do so.
>
>> Pushing a mouse button will revive it (and the event is passed to X).
>
> Which is expected behavior.
>
> Your mouse (as many other mice out there) doesn't emit wakeup event on
> movement, it only does on button click. There is nothing kernel can do
> about it. This is one of the reasons why autosuspend is disabled by
> default (other reason being many devices broken beyond hope when it comes
> to waking up).

Well, to me it seems a regression since it worked correctly in 2.6.29, i.e.
* it was suspended after inactivity (at least according to powertop),
* it resumed operation when it was moved (no need to push a button to
have it working again).
unless 2.6.29 just lied about suspending the mouse.

BTW, I find autosuspend useful to increase the battery life, so at
least with good devices, we should make sure it works.

Corrado

>
> --
> Jiri Kosina
> SUSE Labs
>
>



-- 
__________________________________________________________________________

dott. Corrado Zoccolo                          mailto:czoccolo@gmail.com
PhD - Department of Computer Science - University of Pisa, Italy
--------------------------------------------------------------------------

  reply	other threads:[~2009-04-16 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 21:53 Corrado Zoccolo
2009-04-16 10:15 ` Jiri Kosina
2009-04-16 12:45   ` Corrado Zoccolo [this message]
2009-04-16 13:43     ` Oliver Neukum
2009-04-19 13:29       ` Corrado Zoccolo
2009-04-19 15:50         ` Oliver Neukum

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=4e5e476b0904160545h1f384dbdx4161a0a304ad4c80@mail.gmail.com \
    --to=czoccolo@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.name \
    /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®