From: Felipe Balbi <balbi@ti.com>
To: Brad Parker <brad@heeltoe.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: [PATCH] musb: move usb_add_hcd to the core init code from gadget code (v2)
Date: Mon, 10 Jan 2011 13:57:14 +0200 [thread overview]
Message-ID: <20110110115714.GA5573@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <4D2AF1EE.8010105@heeltoe.com>
Hi,
On Mon, Jan 10, 2011 at 06:47:58AM -0500, Brad Parker wrote:
> I know this is a top post, and a comment on a post from August, but I'd like
> to point out that without this patch I can't get musb host mode to work
> on the beagle board xm (3630).
>
> With this patch, host mode works. If I disconnect and reconnect the port
> goes into "a_idle", which is almost right, and will go into host mode if
> I "echo >/sys/devices/platform/musb_hdrc/mode".
>
> (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)
>
> It seems like few people people test host mode on the omap twl otg port,
> but I have applications which use it...
>
> should this patch get more attention? (there was no response to the
> initial post I could find)
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.
--
balbi
next prev parent reply other threads:[~2011-01-10 11:57 UTC|newest]
Thread overview: 9+ 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 [this message]
2011-01-10 14:08 ` UNS: " Brad Parker
2011-01-10 12:38 ` David Brownell
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=20110110115714.GA5573@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=brad@heeltoe.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 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.