From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] README: add documentation for CONFIG_USB_ULPI*
Date: Wed, 14 Dec 2011 07:51:17 +0200 [thread overview]
Message-ID: <4EE83955.2010308@compulab.co.il> (raw)
In-Reply-To: <CAPnjgZ0reaELyjUEQTJaNcJM7uWJ3yq0B-+m5Lp7kUfKEzkAHw@mail.gmail.com>
Hi Simon,
On 12/14/11 02:28, Simon Glass wrote:
> Hi Igor,
>
> On Mon, Dec 12, 2011 at 2:08 AM, Igor Grinberg <grinberg@compulab.co.il> wrote:
>> Add documentation for CONFIG_USB_ULPI and CONFIG_USB_ULPI_VIEWPORT
>> configuration options.
>>
>> Signed-off-by: Igor Grinberg <grinberg@compulab.co.il>
>> ---
>> README | 8 ++++++++
>> 1 files changed, 8 insertions(+), 0 deletions(-)
>>
>> diff --git a/README b/README
>> index ff72e47..6fe1e0f 100644
>> --- a/README
>> +++ b/README
>> @@ -1185,6 +1185,14 @@ The following options need to be configured:
>> for your device
>> - CONFIG_USBD_PRODUCTID 0xFFFF
>>
>> +- ULPI Layer Support:
>> + The ULPI (UTMI Low Pin (count) Interface) PHYs are supported via
>> + the generic ULPI layer. The generic layer accesses the ULPI PHY
>> + via the platform viewport, so you need both the genric layer and
>> + the viewport enabled. Currently only Chipidea/ARC based
>> + viewport is supported.
>
> Where does it say that only this one is supported in the code?
You mean comments or the code?
> What is specific to that device?
The viewport bits? It is not a part of the ULPI spec.
Other vendors do not have to comply with those.
For example PXA310 has those bits placed and named in some other way...
>
> Regards,
> Simon
>
>> + To enable the ULPI layer support, define CONFIG_USB_ULPI and
>> + CONFIG_USB_ULPI_VIEWPORT in your board configuration file.
>>
>> - MMC Support:
>> The MMC controller on the Intel PXA is supported. To
>> --
>> 1.7.3.4
>>
>
--
Regards,
Igor.
next prev parent reply other threads:[~2011-12-14 5:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 10:08 [U-Boot] [PATCH 0/4] Cleanups and updates for ULPI Igor Grinberg
2011-12-12 10:08 ` [U-Boot] [PATCH 1/4] USB: ULPI: switch argument type from u8 to unsigned Igor Grinberg
2011-12-14 0:25 ` Simon Glass
2011-12-14 6:16 ` [U-Boot] [PATCH v2 " Igor Grinberg
2011-12-16 1:18 ` Simon Glass
2011-12-16 20:02 ` Remy Bohmer
2011-12-12 10:08 ` [U-Boot] [PATCH 2/4] USB: ULPI: clean a mixup of return types Igor Grinberg
2011-12-14 0:26 ` Simon Glass
2011-12-16 20:04 ` Remy Bohmer
2011-12-12 10:08 ` [U-Boot] [PATCH 3/4] USB: ULPI: increase error case verbosity Igor Grinberg
2011-12-14 0:27 ` Simon Glass
2011-12-16 20:06 ` Remy Bohmer
2011-12-12 10:08 ` [U-Boot] [PATCH 4/4] README: add documentation for CONFIG_USB_ULPI* Igor Grinberg
2011-12-14 0:28 ` Simon Glass
2011-12-14 5:51 ` Igor Grinberg [this message]
2011-12-14 19:26 ` Simon Glass
2011-12-15 9:06 ` Igor Grinberg
2011-12-16 20:10 ` Remy Bohmer
2011-12-16 20:29 ` Simon Glass
2011-12-16 20:35 ` Remy Bohmer
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=4EE83955.2010308@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=u-boot@lists.denx.de \
/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