public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Peter Chen <peter.chen@freescale.com>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Matt Porter <matt.porter@linaro.org>
Subject: Re: Disable bus's drivers_autoprobe before rootfs has mounted
Date: Tue, 10 Jun 2014 23:35:07 -0500	[thread overview]
Message-ID: <20140611043507.GA30126@saruman.home> (raw)
In-Reply-To: <20140611041000.GB15184@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

Hi,

On Tue, Jun 10, 2014 at 09:10:00PM -0700, Greg KH wrote:
> > Let's take USB peripheral as an example, there is a device for
> > udc, and a device driver for usb gadget driver, at default, we want
> > the device to be bound to driver automatically, this is what
> > we have done now. But if there are more than one udcs and gadget
> > drivers (eg one B port for mass storage, another B port for usb ethernet),
> > the user may want to have specific binding (eg, udc-0 -> mass storage,
> > udc-1 -> usb ethernet), so the binding will be established
> > after rootfs has mounted. (This feature is implementing)
> 
> Then there better be a way to describe this on the kernel command line
> (i.e. module paramaters), right?  Which is a total mess, why not just
> not bind anything in this case and let the user pick what they want?

you can also blacklist all gadget drivers and manually probe them or -
get this - you can refrain from using gadget drivers and use libusbg to
build the gadget drivers out of raw usb functions, then bind them to the
UDC of your liking.

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2014-06-11  4:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  2:14 Disable bus's drivers_autoprobe before rootfs has mounted Peter Chen
2014-06-11  4:10 ` Greg KH
2014-06-11  3:23   ` Peter Chen
2014-06-11 19:10     ` Greg KH
2014-06-11 19:27       ` Alan Stern
2014-06-12  6:31         ` Peter Chen
2014-06-12 14:12           ` Alan Stern
2014-06-13 10:15             ` Peter Chen
2014-06-13 14:19               ` Alan Stern
2014-06-16  1:36                 ` Peter Chen
2014-06-16 15:00                   ` Alan Stern
2014-06-17  2:04                     ` Peter Chen
2014-06-11  4:35   ` Felipe Balbi [this message]
2014-06-11  3:29     ` Peter Chen
2014-06-11 19:36       ` Felipe Balbi
2014-06-12  7:02         ` Peter Chen
2014-06-12 16:53           ` Felipe Balbi
2014-06-13  7:30             ` Peter Chen

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=20140611043507.GA30126@saruman.home \
    --to=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=matt.porter@linaro.org \
    --cc=peter.chen@freescale.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox