All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: felipe.balbi@nokia.com
Cc: "Gupta, Ajay Kumar" <ajay.gupta@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: usb_nop_xceiv_register() missing when OTG built as modules
Date: Fri, 05 Mar 2010 09:59:52 -0800	[thread overview]
Message-ID: <871vfy3azr.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20100305090426.GG12757@nokia.com> (Felipe Balbi's message of "Fri\, 5 Mar 2010 11\:04\:26 +0200")

Felipe Balbi <felipe.balbi@nokia.com> writes:

> On Thu, Mar 04, 2010 at 06:32:40PM +0100, ext Kevin Hilman wrote:
>>Yes, I did that intentionally.  I *want* USB compiled as a module.  If
>>I do that, the build fails, and that's a bug that needs to be fixed.
>
> it depends on where you're calling usb_nop_xceiv_register(), 

It's called from various board files (board-omap3evm.c,
board-4430sdp.c.)

> if you're calling from a file that's built-into the kernel, then
> it's your fault.

It would be my fault if I wrote those board files.  ;)

> I suggest you keep usb as a module, but keep nop xceiv built-in.

Yes, that's the workaround I'm already using, but it is not a fix.

This dependency breaks the ability to build a minimal kernel with
everything as modules (allmodconfig)

The nop xceiv needs a way for built-in code to register itself for
the cases when no xceiv is built as a module.

Kevin



  reply	other threads:[~2010-03-05 17:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04  0:09 usb_nop_xceiv_register() missing when OTG built as modules Kevin Hilman
2010-03-04  4:29 ` Gupta, Ajay Kumar
2010-03-04 17:32   ` Kevin Hilman
2010-03-05  3:50     ` Gupta, Ajay Kumar
2010-03-05  9:04     ` Felipe Balbi
2010-03-05 17:59       ` Kevin Hilman [this message]
2010-03-05 19:54         ` me
2010-03-05 22:02           ` Kevin Hilman
2010-05-22 23:53             ` Amit Kucheria
2010-05-24  7:07               ` Gupta, Ajay Kumar
2010-05-26  6:03                 ` Felipe Balbi
2010-05-26  6:20                   ` Gupta, Ajay Kumar
2010-05-26  6:53                   ` Gupta, Ajay Kumar
2010-05-26  6:02               ` Felipe Balbi

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=871vfy3azr.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=ajay.gupta@ti.com \
    --cc=felipe.balbi@nokia.com \
    --cc=linux-omap@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 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.