All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jon-hunter@ti.com>
To: "Anders, David" <x0132446@ti.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Gupta, Ajay Kumar" <ajay.gupta@ti.com>,
	"felipe.balbi@nokia.com" <felipe.balbi@nokia.com>
Subject: Re: [PATCH] select NOP_USB_XCEIV for OMAP4
Date: Wed, 23 Jun 2010 17:53:05 -0500	[thread overview]
Message-ID: <4C229051.5090308@ti.com> (raw)
In-Reply-To: <7B4574D56E4ADF438756313E9A172A879A845653@dlee01.ent.ti.com>

On 6/23/2010 4:10 PM, Anders, David wrote:
>> Shouldn't this be a board-specific option, and not set for every
>> OMAP4-based config?
>>
>
> As I understand it, any of the omap4 devices that are using the Inventra need to have at a minimum of the NOP USB Transceiver. Enabling the NOP transceiver doesn't preclude the use of other external transceivers. The NOP USB Transceiver will still need to be registered in the board-specific machine file therefore doesn't impact a board that doesn't use it.

The OMAP4 TRM states:

"The high-speed USB OTG controller supports a single USB port, which 
uses the ULPI interface mode, to connect to an off-chip transceiver 
(12-pin/8-bit data SDR mode) and to connect on D+/D- (+ID) USB bus 
thanks to an embedded USB-HS OTG PHY."

So I read this as you can use either the on-chip PHY or an external PHY. 
Therefore, if you did opt to use an external PHY I am not sure I 
understand why the NOP transceiver I still needed. The OMAP4 an external 
configuration looks the same as OMAP3 to me...

Cheers
Jon

  reply	other threads:[~2010-06-23 22:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 18:47 [PATCH] select NOP_USB_XCEIV for OMAP4 David Anders
     [not found] ` <1277318873-8260-1-git-send-email-x0132446-l0cyMroinI0@public.gmane.org>
2010-06-23 20:33   ` Kevin Hilman
2010-06-23 21:10     ` Anders, David
2010-06-23 22:53       ` Jon Hunter [this message]
     [not found]     ` <87k4ppqyk2.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2010-06-23 21:12       ` Koen Kooi
2010-06-23 22:15         ` Sergei Shtylyov
     [not found]         ` <61951E1F-DEBF-450C-AF06-E0119DA3B33E-oe7qfRrRQfcdWmXj+hCI//P6llvjuJOh@public.gmane.org>
2010-06-23 22:56           ` Jon Hunter
2010-06-23 23:03           ` Gadiyar, Anand
2010-06-24 14:38             ` Anders, David
     [not found]               ` <7B4574D56E4ADF438756313E9A172A879A8E0D9E-bGftbgMkZa+IQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2010-06-24 15:53                 ` Gadiyar, Anand
     [not found]                   ` <5A47E75E594F054BAF48C5E4FC4B92AB032366B0EA-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2010-06-24 17:14                     ` Anders, David
2010-06-24 18:43               ` Kevin Hilman
2010-06-23 22:11   ` Sergei Shtylyov

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=4C229051.5090308@ti.com \
    --to=jon-hunter@ti.com \
    --cc=ajay.gupta@ti.com \
    --cc=felipe.balbi@nokia.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=x0132446@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.