All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Gatliff <bgat@billgatliff.com>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: "Gadiyar, Anand" <gadiyar@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"beagleboard@googlegroups.com" <beagleboard@googlegroups.com>
Subject: Re: Anyone using an ISP1505?
Date: Mon, 21 Dec 2009 13:47:55 -0600	[thread overview]
Message-ID: <4B2FD0EB.7030005@billgatliff.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608703001E1949@dbde02.ent.ti.com>

Pandita, Vikram wrote:
> Bill
>  There is a basic confusion whether you are using MUSB OTG core of omap 
> Or are you using EHCI core of omap.
>
> Both can be connected to a ULPI PHY and so you need to be very precise?
>   

I'm on the CUS package, and the D0 pin of the PHY is tied to pad T24 of
the OMAP3530.  That's the ULPI D0 for EHCI, right?

If the pad can be multiplexed between both MUSB and EHCI, how can I tell
which one is connected there now?  For that matter, where in the
mountains of OMAP3xxx documentation does it say which controller the UH0
pins are tied to?  I haven't found it yet...


Thanks!


b.g.

-- 
Bill Gatliff
bgat@billgatliff.com


  reply	other threads:[~2009-12-21 19:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 19:01 Anyone using an ISP1505? Bill Gatliff
2009-12-17 19:10 ` Felipe Balbi
2009-12-18 19:13   ` Bill Gatliff
2009-12-17 19:20 ` Gadiyar, Anand
2009-12-18 19:10   ` Bill Gatliff
2009-12-18 19:20     ` Pandita, Vikram
2009-12-21 17:06       ` Bill Gatliff
2009-12-21 19:43         ` Pandita, Vikram
2009-12-21 19:47           ` Bill Gatliff [this message]
2009-12-21 20:12             ` Gadiyar, Anand
2009-12-21 20:42               ` Felipe Balbi
2009-12-21 20:57                 ` Gadiyar, Anand
2009-12-19 10:05     ` Gadiyar, Anand

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=4B2FD0EB.7030005@billgatliff.com \
    --to=bgat@billgatliff.com \
    --cc=beagleboard@googlegroups.com \
    --cc=gadiyar@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=vikram.pandita@ti.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.