[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <499A89AD.6010704@free.fr>
Date: Tue, 17 Feb 2009 10:55:57 +0100
From: Laurent Riffard <laurent.riffard@...e.fr>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Oliver Neukum <oliver@...kum.org>
CC: linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
USB list <linux-usb@...r.kernel.org>
Subject: linux-next: USB mouse won't work after resume.
Hello,
My USB mouse won't work after suspend to disk and resume. I must unload and reload the ohci_hcd module to get it back.
I made a bisection, reverting the following commit does fix the behaviour:
commit 8390887fae55be9c06e3f064464d2bc8e908b8df
Author: Oliver Neukum <oliver@...kum.org>
Date: Wed Dec 17 15:38:03 2008 +0100
HID: autosuspend support for USB HID
This uses the USB busy mechanism for aggessive autosuspend of USB
HID devices. It autosuspends all opened devices supporting remote wakeup
after a timeout unless
- output is being done to the device
- a key is being held down (remote wakeup isn't triggered upon key release)
- LED(s) are lit
- hiddev is opened
As in the current driver closed devices will be autosuspended even if they
don't support remote wakeup.
The patch is quite large because output to devices is done in hard interrupt
context meaning a lot a queuing and locking had to be touched. The LED stuff
has been solved by means of a simple counter. Additions to the generic HID code
could be avoided. In addition it now covers hidraw. It contains an embryonic
version of an API to let the generic HID code tell the lower levels which
capabilities with respect to power management are needed.
Signed-off-by: Oliver Neukum <oneukum@...e.de>
Signed-off-by: Jiri Kosina <jkosina@...e.cz>
attached: .config
~~
laurent
View attachment "config-2.6.29-rc5-next-20090216" of type "text/plain" (57849 bytes)
Powered by blists - more mailing lists