Hi,
On Mon, Dec 21, 2009 at 09:12:15PM +0100, ext Gadiyar, Anand wrote:
Bill Gatliff wrote:
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?
No confusion for me. I took the liberty of looking this up, and for
this package, T24 is D0 for MUSB, not EHCI.
If the pad can be multiplexed between both MUSB and EHCI, how can I tell
which one is connected there now?
No pad in the OMAP3 is multiplexed between both MUSB and EHCI; HSUSB0
is MUSB (this makes sense, since most users of the OMAP3 would like
to use the OMAP3 as a USB peripheral, and there is only one peripheral
controller, so the MUSB lines are usually not switches to other roles.
EHCI on the other hand is on HSUSB1 to HSUSB3 (there are 3 ports).
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...
Well, in the USB chapter of the OMAP3 TRM, the very first figure
(24.1 - USB modules overview) shows this clearly. Port0 is MUSB,
and Ports 1-3 are HSUSB Host.
Are you just missing to call usb_nop_xceiv_register() ??
can you attach your .config file to the mail ??
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
