[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110426205950.GD20381@suse.de>
Date: Tue, 26 Apr 2011 13:59:50 -0700
From: Greg KH <gregkh@...e.de>
To: Sarah Sharp <sarah.a.sharp@...ux.intel.com>
Cc: Alan Stern <stern@...land.harvard.edu>,
Tanya Brokhman <tlinder@...eaurora.org>,
linux-arm-msm@...r.kernel.org, ablay@...eaurora.org, balbi@...com,
USB list <linux-usb@...r.kernel.org>,
Kernel development list <linux-kernel@...r.kernel.org>,
'Matthew Wilcox' <matthew.r.wilcox@...el.com>
Subject: Re: [RFC/PATCH v3 2/5] uas: MS UAS Gadget driver - Infrastructure
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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists