On Thu, 10 Oct 2019, Bastien Nocera wrote: > On Wed, 2019-10-09 at 14:45 -0400, Alan Stern wrote: > > > On Wed, 9 Oct 2019, Bastien Nocera wrote: > > > > <snip> > > > + return > > device_driver_attach(usb_generic_driver.drvwrap.driver, dev); > > > + return error; > > > > I think that's right. A little testing wouldn't hurt. > > device_driver_attach() isn't available to this part of the code. > > I think the only way to do things here might be to set status bit for > the usb_device and launch device_reprobe(). The second time around, we > wouldn't match or probe the specific driver. That would mean probing generic_driver twice, right? You probably should call its disconnect routine in between. That sounds pretty awkward, but if there's no other way then go ahead and do it. Ala Stern
