On Mon, Jun 08, 2009 at 08:05:56PM -0400, Alan Stern wrote: > On Tue, 9 Jun 2009, Matthew Garrett wrote: > > The needs_binding option only seems to be set in the case where > > USB_QUIRK_RESET_RESUME is present but there's no reset_resume callback > > in the driver? I don't have enough experience of the USB core to know > > what that's actually doing. > > needs_binding is private to usbcore; it shouldn't be used by drivers. > It gets set when usbcore has to unbind a driver because the driver > doesn't support suspend, resume, or reset_resume, and then later on it > causes usbcore to probe for new drivers after the device has been > resumed or reset. Ok. I'll experiment some more with that. > > The card comes up in a dumb state and then gets fed 16MB worth of armel > > ELF object which causes it to reboot into a more useful form. It stays > > in that state until the power plane is entirely cut, which happens in > > system suspend but not in autosuspend. > > It shouldn't happen in system suspend. Why doesn't the system provide > suspend current to the USB bus? Unsure - perhaps vendors think it'll consume too much power in that case? My machine has a kill switch option (controllable via software) that forces a full power cut, which seems equivalent to the suspend cycle. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- 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
