linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "ABRAHAM, KISHON VIJAY" <kishon@ti.com>
To: balbi@ti.com
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/9] scripts/modpost: add a exception for USB gadget drivers
Date: Thu, 16 Aug 2012 19:56:19 +0530	[thread overview]
Message-ID: <CAAe_U6LEs3W7PoTmRrD9nEdjB=0RvGpXaw5MffbeL-yS52EdEQ@mail.gmail.com> (raw)
In-Reply-To: <20120816130344.GD26408@arwen.pp.htv.fi>

On Thu, Aug 16, 2012 at 6:33 PM, Felipe Balbi <balbi@ti.com> wrote:
> On Thu, Aug 16, 2012 at 06:35:07PM +0530, ABRAHAM, KISHON VIJAY wrote:
>> Hi Sebastian,
>>
>> On Thu, Aug 16, 2012 at 1:29 AM, Sebastian Andrzej Siewior
>> <bigeasy@linutronix.de> wrote:
>> > The "driver" struct for a gadget driver is named *_driver. On module
>> > load, the gadget expects a UDC driver to be loaded and avaiable. If this
>> > is not the case => -ENODEV and bye bye. That means that the gadget
>> Will this be taken care of in your future series (with configfs?).
>> There might be cases when your gadget driver gets loaded before the
>> UDC driver.
>
> with configfs that won't be a problem because even though function
> drivers are loaded, they won't bind to any controller until we tell them
> to through configfs. IOW, functions will only bind to UDCs after we
> assign them to a particular usb interface through configfs.

Ok. Makes sense..

Thanks
Kishon

      reply	other threads:[~2012-08-16 14:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1345060759-18091-1-git-send-email-bigeasy@linutronix.de>
2012-08-15 19:59 ` [PATCH 2/9] scripts/modpost: add a exception for USB gadget drivers Sebastian Andrzej Siewior
2012-08-15 20:14   ` Sam Ravnborg
2012-08-17 15:36     ` Sebastian Andrzej Siewior
2012-08-16 13:05   ` ABRAHAM, KISHON VIJAY
2012-08-16 13:03     ` Felipe Balbi
2012-08-16 14:26       ` ABRAHAM, KISHON VIJAY [this message]

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='CAAe_U6LEs3W7PoTmRrD9nEdjB=0RvGpXaw5MffbeL-yS52EdEQ@mail.gmail.com' \
    --to=kishon@ti.com \
    --cc=balbi@ti.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).