On Tuesday 22 June 2010, Oliver Neukum wrote:

Am Dienstag, 22. Juni 2010, 13:06:12 schrieb Ondrej Zary:

quoted

On Friday 18 June 2010, Oliver Neukum wrote:

quoted

Am Freitag, 18. Juni 2010 20:34:03 schrieb Ondrej Zary:

quoted

On Friday 18 June 2010 20:22:07 Oliver Neukum wrote:

quoted

Am Donnerstag, 10. Juni 2010 16:13:51 schrieb Ondrej Zary:

quoted

quoted

quoted

I haven't tested the patches before. Now I tested them and
the Nexio touchscreen does not play well with suspend. It
always reconnects after resume from STR or hibernation.
Autosuspend is probably never activated at the URBs are
submitted continuously.

I see. Can you compile with CONFIG_USB_DEBUG and send me the
log?

This can't be fixed - no matter what you do, the device
reconnects if you stop talking to it.

Have you tried setting it back to config 0?

No, I haven't. It reconnects even if there's no driver loaded (e.g.
older kernel). I don't know if kernel sets configuration on all USB
devices upon connect (even if there's no driver).

Yes, the kernel sets a configuration if the power budget allows it.
You can set it back to 0 through sysfs and see what happens.

It disconnects and reconnects after bConfigurationValue is set to 0.

This is a violation of the spec. Can you give me the IDs so that I can
put the devices into the quirks file? Or can I take this from the driver?
Do all devices that marked as always needing an irq transfer behave
this way?

This is not a bug surprise as this device is broken in many ways. It takes 
ages to detect and identify and looks like cdc_acm. The pseudo-multitouch 
capable protocol is pretty bad too. Also there are some reports about devices 
using the same ID but different protocol.

I have only one - 1870:0001, don't know anything about the other.

-- 
Ondrej Zary
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html