public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Parker <brad@heeltoe.com>
To: balbi@ti.com
Cc: bryan.wu@canonical.com, felipe.balbi@nokia.com,
	linux-usb@vger.kernel.org, david-b@pacbell.net,
	kernel-team@lists.ubuntu.com, linux-kernel@vger.kernel.org,
	ricardo.salveti@canonical.com, linux-omap@vger.kernel.org
Subject: Re: UNS: Re: [PATCH] musb: move usb_add_hcd to the core init code from gadget code (v2)
Date: Mon, 10 Jan 2011 09:08:17 -0500	[thread overview]
Message-ID: <4D2B12D1.5060807@heeltoe.com> (raw)
In-Reply-To: <20110110115714.GA5573@legolas.emea.dhcp.ti.com> (sfid-20110110_070231_150867_75CADAA4)

Felipe Balbi wrote:
> Hi,
>
> On Mon, Jan 10, 2011 at 06:47:58AM -0500, Brad Parker wrote:
>   
>> ...
>> (my expectation is that the mode should toggle from "b_idle" to "a_host"
>> when I plug in an a connector with the id pin tied correctly, and
>> back to "b_idle"
>> when I disconnect)
>>     
> What's the problem in simply insmoding a gadget driver ? If you have OTG
> enabled, you _need_ a gadget driver to have a fully working setup. If
> you want host only, then change Kconfig
I guess there are multiple "modalities".

- some users don't use a gadget driver and expect host mode to work 
(they fail)
- some users use a gadget driver and host mode (apparently that works)
- some users use a gadget driver only (they work)

I'd  like to avoid having multiple kernels.  (and to be honest, I'm not 
convinced
just convince I can get the right behaviors by changing the .config; I 
assume
you mean .config and not Kconfig...  I don't think it works but I'll try 
it out)

-brad


  reply	other threads:[~2011-01-10 14:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23 14:36 [PATCH] musb: move usb_add_hcd to the core init code from gadget code (v2) Bryan Wu
2010-07-23 15:28 ` Sergei Shtylyov
2010-07-30  4:53   ` Bryan Wu
2010-08-09 13:24 ` Bryan Wu
2011-01-10 11:47   ` Brad Parker
2011-01-10 11:57     ` Felipe Balbi
2011-01-10 14:08       ` Brad Parker [this message]
2011-01-10 12:38     ` David Brownell

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=4D2B12D1.5060807@heeltoe.com \
    --to=brad@heeltoe.com \
    --cc=balbi@ti.com \
    --cc=bryan.wu@canonical.com \
    --cc=david-b@pacbell.net \
    --cc=felipe.balbi@nokia.com \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ricardo.salveti@canonical.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