public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan Wu <bryan.wu@canonical.com>
To: David Brownell <david-b@pacbell.net>
Cc: felipe.balbi@nokia.com, linux-usb@vger.kernel.org,
	kernel-team@lists.ubuntu.com, linux-kernel@vger.kernel.org,
	ricardo.salveti@canonical.com
Subject: Re: [PATCH] musb: move usb_add_hcd to the core init code from gadget code
Date: Fri, 23 Jul 2010 18:50:45 +0800	[thread overview]
Message-ID: <4C497405.9010805@canonical.com> (raw)
In-Reply-To: <94320.67137.qm@web180312.mail.gq1.yahoo.com>

On 07/23/2010 05:53 PM, David Brownell wrote:
> Are you sure this doesn't break the hardware
> initialization sequencing on some chips?
>

We tested on our Beagle board C3/C4 board and will test that on Beagle XM board 
and OMAP4 board. Since I still got a Blackfin BF527 board, I will help to test.

For other silicons, I'm not sure about that.

> I distinctly call losing over a month of development
> time on this issue, because the hardware has some
> undocumented constraints in this area.  The entire
> reeason the host init is so "late" is that doing
> it earlier (at more logically sensible moments, (in
> terms of USB specs vs Mentor silicon) broke things.
>

Yeah, that's frustrated. I also spent several days here to find a solution to 
this. I saw the comments in the code about that undocumented constraints. But 
that maybe depends on different silicon.

Thanks, Dave.
-Bryan


      reply	other threads:[~2010-07-23 10:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23  9:36 [PATCH] musb: move usb_add_hcd to the core init code from gadget code Bryan Wu
2010-07-23  9:53 ` David Brownell
2010-07-23 10:50   ` Bryan Wu [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=4C497405.9010805@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 \
    /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