From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: [RFC/PATCH v3 2/5] uas: MS UAS Gadget driver - Infrastructure Date: Tue, 26 Apr 2011 13:59:50 -0700 Message-ID: <20110426205950.GD20381@suse.de> References: <20110426172559.GA5405@xanatos> <20110426200625.GB5405@xanatos> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20110426200625.GB5405@xanatos> Sender: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Sarah Sharp Cc: Alan Stern , Tanya Brokhman , linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, ablay-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, balbi-l0cyMroinI0@public.gmane.org, USB list , Kernel development list , 'Matthew Wilcox' List-Id: linux-arm-msm@vger.kernel.org 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-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html