From: Bryan Wu <bryan.wu@canonical.com>
To: Sergei Shtylyov <sshtylyov@mvista.com>, felipe.balbi@nokia.com
Cc: linux-usb@vger.kernel.org, kernel-team@lists.ubuntu.com,
linux-kernel@vger.kernel.org, ricardo.salveti@canonical.com,
david-b@pacbell.net
Subject: Re: [PATCH] musb: move usb_add_hcd to the core init code from gadget code (v2)
Date: Fri, 30 Jul 2010 12:53:03 +0800 [thread overview]
Message-ID: <4C525AAF.6020102@canonical.com> (raw)
In-Reply-To: <4C49B529.8080408@ru.mvista.com>
On 07/23/2010 11:28 PM, Sergei Shtylyov wrote:
> Hello.
>
> Bryan Wu wrote:
>
>> BugLink: http://bugs.launchpad.net/bugs/608312
>
>> v2:
>> fix the building error on latest 2.6.35-rc kernel, since v1 was
>> generated in
>> 2.6.33 kernel.
>
> The remarks about patch changes should follow the --- tear line.
>
Thanks Sergei, I will take care of it in the future.
Any other comments about this patch?
Felipe, could you please take a look? or need I ping you in the Facebook, -:))
-Bryan
>> v1:
>> usb_add_hcd was only called when we insmod the gadget class module or
>> built-in
>> that gadget class driver. If musb is configured as OTG controller, we
>> need to
>> insmod or built-in gadget class driver to make our Host mode fucntion
>> works.
>
>> In our Ubuntu system, normally we compiled all the gadget class
>> drivers as
>> modules. Then users can insmod the gadget modules as they want. But
>> without the
>> gadget class driver running, we needs host function to support common USB
>> devices.
>
>> This patch fix this issue and tested on omap3 beagle board and Gumstix
>> board.
>
>> Signed-off-by: Bryan Wu <bryan.wu@canonical.com>
>
> WBR, Sergei
next prev parent reply other threads:[~2010-07-30 4:53 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 [this message]
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 ` UNS: " Brad Parker
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=4C525AAF.6020102@canonical.com \
--to=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-usb@vger.kernel.org \
--cc=ricardo.salveti@canonical.com \
--cc=sshtylyov@mvista.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