public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: me@felipebalbi.com
Cc: Kevin Hilman <khilman@mvista.com>, linux-omap@vger.kernel.org
Subject: Re: OMAP3430: MUSB host and hot-plugging
Date: Thu, 20 Mar 2008 13:25:28 -0700	[thread overview]
Message-ID: <200803201325.28818.david-b@pacbell.net> (raw)
In-Reply-To: <20080320200000.GI4772@kedavra.cpe.vivax.com.br>

On Thursday 20 March 2008, Felipe Balbi wrote:
> Could it be some
> problem in the ULPI support for omap3 that's preventing musb to wake up
> and switch to host role ?

Your theory is as good as mine; I don't have that hardware.

I was just pointing out that this specific area has always
been a significant PITA for the MUSB silicon ... I'm not the
only developer who's ended up losing weeks of time chasing
(undocumented) bogosity in the area of host-side startup.

The thing is that making it "switch to host role" is the
very black magic that regularly misbehaved.  ISTR there was
a chicken/egg thing going on:  it couldn't know it needed to
switch to "host role" unless the oddball Mentor "session"
was already active, but it couldn't be activated unless you
somehow knew it should be in host role...



  reply	other threads:[~2008-03-20 20:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20  0:14 OMAP3430: MUSB host and hot-plugging Kevin Hilman
2008-03-20 19:30 ` David Brownell
2008-03-20 20:00   ` Felipe Balbi
2008-03-20 20:25     ` David Brownell [this message]
2008-03-20 20:48       ` Felipe Balbi
2008-03-24  9:27       ` Pandita, Vikram
  -- strict thread matches above, loose matches on Subject: below --
2008-03-20 12:27 Felipe Balbi
2008-03-20 12:34 ` Pandita, Vikram
2008-03-20 12:38   ` Felipe Balbi
2008-03-20 12:47     ` Pandita, Vikram
2008-03-20 12:55       ` Felipe Balbi
2008-03-20 17:11       ` Kevin Hilman
2008-03-20 18:57         ` 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=200803201325.28818.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=khilman@mvista.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=me@felipebalbi.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