On Thu, Aug 29, 2013 at 02:59:50AM +0800, Alan Stern wrote: > On Wed, 28 Aug 2013, Greg Kroah-Hartman wrote: > > > On Wed, Aug 28, 2013 at 01:13:46PM -0400, Alan Stern wrote: > > > On Wed, 28 Aug 2013, Greg Kroah-Hartman wrote: > > > > > > > > [Q] Why the special devices are only mice? Would high speed devices > > > > > such as 3G modem or USB Bluetooth adapter trigger this issue? > > > > > - Current this sensitivity is only confined to devices that use Pixart > > > > > controllers. This controller is designed for use with LS mouse > > > > > devices only. We have not observed any other devices failing. There > > > > > may be a small risk for other devices also but this patch (reset > > > > > device in resume phase) will cover the cases if required. > > > > > > > > Then just do this "quirk" for Pixart controller devices. Don't penalize > > > > everyone else. > > > > > > Is there any way to detect when a device uses a Pixart controller? I > > > don't see how you could tell. > > > > Vendor device id should tell you what you need to know, right? > > Not necessarily. Manufacturers often get their USB hardware from other > suppliers and then overwrite the vendor and product IDs in the firmware > with their own. > > Of course, I don't know if that's true in this case. The guys at AMD > should be able to tell easily enough; they have a bunch of these mice > to test with. > Yes, I tested many mice (lenovo, HP, Logitech and etc.) which triggered this issue, some of them's iManufacture field mark "Pixart" and some of them's overwrite by Manufacturers. And idVendor and idProduct are different. I don't find a perfect flag to distinguish the devices with Pixart controller. Is there any idea? Thanks, Rui -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
