On Fri, 22 Jun 2007, Oliver Neukum wrote:

> could you please run two tests?
> 1. set the autosuspend timeout to 0 (this'll kill usb mice)

And it kills also my testing keyboard on the UHCI system. After the 
keyboard gets suspended and I hit a key, it wakes up (the LEDs come up), 
but no keypressess are produced and the keyboard gets suspended again.

> 2. use a 1.1 hub

I grabbed a random HUB (usbhub4c from Linksys) and this made it work 
nicely even on UHCI-based system I am testing on.

I will do some more debugging to check what exactly goes wrong, but I am 
leaving for OLS tomorrow.


BTW I don't know if you recall - I reported previously that the keypresses 
are lost only if I try to hit the key very soon after the keyboard gets 
suspended. If I wait for 2 seconds (looks like exact value), then no 
keypressess are lost and the keyboard wakes up properly.

When I change the autosuspend values of all devices in system from 2 
(default) to 5, the value described in the previous paragraph (i.e. the 
minimum time for which the keyboard must be suspended before it could be 
woken up flawlessly) is still 2 seconds.

-- 
Jiri Kosina

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to