Re: [RFC/PATCH v3 2/5] uas: MS UAS Gadget driver - Infrastructure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 26, 2011 at 01:06:25PM -0700, Sarah Sharp wrote:
> > One can always unbind usb-storage from an interface and bind uas to
> > that interface by hand, using sysfs.  At the moment there doesn't 
> > appear to be any mechanism for doing this automatically.  For example, 
> > usb-storage _could_ choose not to bind to an interface if there's a UAS 
> > altsetting -- but currently it doesn't take that into account.
> 
> How would the usb-storage driver reject a bind by the USB core?  By
> returning an error from the probe function?

Yes.

> Would the USB core go and search for the next driver after the BOT
> driver rejected the bind?

Yes.

> It looks like usb_probe_interface will just return an error if the
> first driver's probe function fails.

The driver core continues on and will probe the remaining drivers for
that bus.  Also, when a new driver shows up, the driver core asks if any
of the unbound devices should be bound to this new driver.

So you should be fine.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [Linux for Sparc]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux