On Thu, 11 Oct 2012, Sarah Sharp wrote: > When LPM fails, the device often goes into the Inactive state, which > also marks the port as not connected. The USB core will issue a warm > reset to the device and then do a logical disconnect. VIA hubs come > back fine after the warm reset, but that does mean the user will see a > disconnect and reconnect of devices beneath the tree. Kind of a bummer if this happens while you've got a filesystem mounted on the device... > > Also, how annoying will it be for users if their device fails and has > > to be reset (or replugged) every time they boot? > > Yep, you're right that it would be pretty annoying. I'm leaning towards > the static blacklist in the kernel. > > One of the things I've found out is that VIA hubs keep their firmware > revision in the bcdDevice field of their device descriptor. If I find > one version of the VIA firmware works with LPM, can the quirks table > create a rule that would effectively be something like "bcdDevice < > 0x9a90"? Yes. A usb_device_id can specify upper and lower limits for a bcdDevice range. Alan Stern -- 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
