From: "Dâniel Fraga" <fragabr@gmail.com>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: linux-input@vger.kernel.org
Subject: Re: 3.5.1 hid_generic causes mouse locking until a button is clicked
Date: Sun, 12 Aug 2012 18:16:22 -0300 [thread overview]
Message-ID: <50281d29.516eec0a.683e.1052@mx.google.com> (raw)
In-Reply-To: <20120812195329.2cb454c3@neptune.home>
On Sun, 12 Aug 2012 19:53:29 +0200
Bruno Prémont <bonbons@linux-vserver.org> wrote:
> This might be USB-autosuspend. 2 seconds seems to match the default
> delay for autosuspending USB devices.
Hi Bruno. That's it!
I raised the autosuspend value and I'm using it as a
workaround... but the default values are the same as the kernel 3.4.4
values, so something has changed:
/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/power$ cat
autosuspend*
2 <----- autosuspend
2000 <-- autosuspend_delay_ms
So, if the values are the same, why the behaviour has changed
from kernel 3.4 to 3.5?
I mean, it seems that with kernel 3.4 simply moving the mouse
would wake up the usb port and now with kernel 3.5 it only works if I
press a button.
So, kernel 3.5 is supposed to wake up the usb port when we move
the mouse or not?
Is there a way to restore the old behaviour from kernel 3.4?
Thanks.
--
Linux 3.5.1: Saber-toothed Squirrel
http://www.youtube.com/DanielFragaBR
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-08-12 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-11 19:55 3.5.1 hid_generic causes mouse locking until a button is clicked Dâniel Fraga
2012-08-12 17:53 ` Bruno Prémont
2012-08-12 21:16 ` Dâniel Fraga [this message]
2012-08-13 6:30 ` Oliver Neukum
2012-08-13 9:18 ` Dâniel Fraga
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=50281d29.516eec0a.683e.1052@mx.google.com \
--to=fragabr@gmail.com \
--cc=bonbons@linux-vserver.org \
--cc=linux-input@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).