On Wed, Jul 18, 2012 at 10:52:22AM -0400, Alan Stern wrote: > On Wed, 18 Jul 2012, Oliver Neukum wrote: > > > On Wednesday 18 July 2012 10:21:27 Alan Stern wrote: > > > On Wed, 18 Jul 2012, Oliver Neukum wrote: > > > > > > > > I have a question that reset-resume still can not resolve firmware > > > > > problem? I think this depend on driver. right? > > > > > > > > Right, but this is not really useful information. We can infer from > > > > a lack of support for reset_resume() that we must not cut power. > > > > The reverse conclusion is invalid, unfortunately. > > > > > > Why? If the driver claims to support reset-resume then it must have a > > > way to insure that firmware is reloaded when necessary. > > > > No, the device may morph. And we have generic drivers (btusb) that > > support devices after another driver (ath3k) has uploaded firmware. > > True. This would be a case where unbinding the driver is the only safe > way to go. Hmm, but wouldn't both the bluetooth and wireless device have remote wakeup enabled when it was suspended? That would mean that we couldn't power off the port. Sarah Sharp -- 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
