At Wed, 26 Nov 2014 11:10:23 +0100, Oliver Neukum wrote: > > On Wed, 2014-11-26 at 09:52 +0100, Takashi Iwai wrote: > > At Wed, 26 Nov 2014 14:15:27 +0900, > > > In order to paper over this, we may also remember the failing firmware > > and avoid loading it. This might be an easer way than the endless > > fight against UMH race... > > Hi, > > the full fix would be to implement reset_resume() for btusb. > It seems to me that setup() should be split in two methods, > one to request the firmware from user space and the second > to transfer it to the device. reset_resume() would just need > to repeat the second operation. I'm not against it, but one slight drawback is that you'll have to remember the firmware content to transfer by the driver itself in this scenario. In the firmware loader framework, the content is re-read at resume so that the largish content isn't kept unnecessarily during the whole operation. Takashi -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
