From: Greg KH <gregkh-l3A5Bk7waGM@public.gmane.org>
To: Sarah Sharp <sarah.a.sharp-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: Alan Stern
<stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>,
Tanya Brokhman <tlinder-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ablay-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
balbi-l0cyMroinI0@public.gmane.org,
USB list <linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Kernel development list
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
'Matthew Wilcox'
<matthew.r.wilcox-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [RFC/PATCH v3 2/5] uas: MS UAS Gadget driver - Infrastructure
Date: Tue, 26 Apr 2011 13:59:50 -0700 [thread overview]
Message-ID: <20110426205950.GD20381@suse.de> (raw)
In-Reply-To: <20110426200625.GB5405@xanatos>
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
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@suse.de>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Tanya Brokhman <tlinder@codeaurora.org>,
linux-arm-msm@vger.kernel.org, ablay@codeaurora.org,
balbi@ti.com, USB list <linux-usb@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>,
"'Matthew Wilcox'" <matthew.r.wilcox@intel.com>
Subject: Re: [RFC/PATCH v3 2/5] uas: MS UAS Gadget driver - Infrastructure
Date: Tue, 26 Apr 2011 13:59:50 -0700 [thread overview]
Message-ID: <20110426205950.GD20381@suse.de> (raw)
In-Reply-To: <20110426200625.GB5405@xanatos>
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
next prev parent reply other threads:[~2011-04-26 20:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 13:36 [RFC/PATCH v3 2/5] uas: MS UAS Gadget driver - Infrastructure Tatyana Brokhman
2011-04-14 13:36 ` Tatyana Brokhman
[not found] ` <1302788176-27972-1-git-send-email-tlinder-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-04-14 17:31 ` Alan Stern
2011-04-14 17:31 ` Alan Stern
2011-04-14 17:40 ` Greg KH
2011-04-16 17:10 ` Tanya Brokhman
2011-04-16 17:10 ` Tanya Brokhman
2011-04-14 17:41 ` Greg KH
2011-04-18 19:37 ` Sarah Sharp
2011-04-19 10:30 ` Tanya Brokhman
2011-04-19 10:30 ` Tanya Brokhman
2011-04-26 9:00 ` Tanya Brokhman
2011-04-26 9:00 ` Tanya Brokhman
2011-04-26 17:25 ` Sarah Sharp
2011-04-26 17:25 ` Sarah Sharp
2011-04-26 18:40 ` Alan Stern
2011-04-26 18:40 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1104261423250.2035-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2011-04-26 20:06 ` Sarah Sharp
2011-04-26 20:06 ` Sarah Sharp
2011-04-26 20:59 ` Greg KH [this message]
2011-04-26 20:59 ` Greg KH
2011-04-27 17:16 ` Alan Stern
2011-04-27 17:16 ` Alan Stern
2011-04-28 5:54 ` Tanya Brokhman
2011-04-28 5:54 ` Tanya Brokhman
2011-04-28 14:13 ` Alan Stern
2011-04-28 14:13 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110426205950.GD20381@suse.de \
--to=gregkh-l3a5bk7wagm@public.gmane.org \
--cc=ablay-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matthew.r.wilcox-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=sarah.a.sharp-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org \
--cc=tlinder-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.