From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7] USB: Add generic ULPI layer and a viewport
Date: Wed, 07 Dec 2011 20:16:58 +0200 [thread overview]
Message-ID: <4EDFAD9A.3050304@compulab.co.il> (raw)
In-Reply-To: <201112071827.48767.marek.vasut@gmail.com>
Hi Marek,
On 12/07/11 19:27, Marek Vasut wrote:
>> On 12/07/11 03:42, Simon Glass wrote:
>>> Hi Igor,
>>>
>>> Looks good - a few comments from me.
>>>
>>> On Mon, Dec 5, 2011 at 1:07 AM, Igor Grinberg <grinberg@compulab.co.il>
> wrote:
>>>> From: Jana Rapava <fermata7@gmail.com>
>>>>
>>>> Add partial ULPI specification implementation that should be enough to
>>>> interface the ULPI PHYs in the boot loader context.
>>>> Add a viewport implementation for Chipidea/ARC based controllers.
>>>>
>>>> Signed-off-by: Jana Rapava <fermata7@gmail.com>
>>>> Signed-off-by: Igor Grinberg <grinberg@compulab.co.il>
>>>> Cc: Remy Bohmer <linux@bohmer.net>
>>>> Cc: Stefano Babic <sbabic@denx.de>
>>>> Cc: Wolfgang Grandegger <wg@denx.de>
>>>> Cc: Simon Glass <sjg@chromium.org>
>>>> ---
[...]
>>> Just out of interest, is it possible to test this? How would I plumb it
>>> in?
>>
>> Well, from my experience with ULPI hardware,
>> I think the controller specific glue looks like the right place
>> for putting the ULPI layer calls in.
>>
>> In general, the controller code knows which PHYs it supports
>> and board code knows which PHY is assembled on the board,
>> so it is not that straight simple to find the right place.
>>
>> I think, Marek has patches that supposed to use this framework on efikamx
>> board.
>
> I tried using the interface, but the design seems completely wrong :-( Jana was
> supposed to design it mainly for the efikamx board, but this interface is
> unusable there.
May I ask you why?
Isn't it because of that nasty VBUS bug efikamx has?
You can't say the design is wrong if it is more generic then you want...
> I had to fall back to basic ulpi_read()/ulpi_write() calls :-(
That's too bad.
Because ulpi_{read|write}() is only a viewport implementation and
it is not following the ULPI spec.
> I'm afraid we won't make it for .12 release window with this patches ... very
> bad :-( I'll try talking to WD if he can push the release window to allow this
Good.
> (or redesigned version) in, but I don't know if that's a good idea.
I don't think it should be redesigned.
Currently, it is generic and abstracts the ULPI specification nicely.
It can be used on any architecture.
I have already stated in the cover letter,
what IMO is missing to improve usability, but that will not be a problem.
Do you have the efikamx patches somewhere I can look at?
--
Regards,
Igor.
next prev parent reply other threads:[~2011-12-07 18:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 9:06 [U-Boot] [PATCH v7] Add generic ULPI layer Igor Grinberg
2011-12-05 9:07 ` [U-Boot] [PATCH v7] USB: Add generic ULPI layer and a viewport Igor Grinberg
2011-12-06 23:49 ` Marek Vasut
2011-12-07 1:42 ` Simon Glass
2011-12-07 13:38 ` Igor Grinberg
2011-12-07 17:27 ` Marek Vasut
2011-12-07 18:16 ` Igor Grinberg [this message]
2011-12-07 18:36 ` Marek Vasut
2011-12-07 19:12 ` Igor Grinberg
2011-12-06 23:49 ` [U-Boot] [PATCH v7] Add generic ULPI layer Marek Vasut
2011-12-07 12:59 ` Igor Grinberg
2011-12-07 13:43 ` Igor Grinberg
2011-12-07 17:28 ` Marek Vasut
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=4EDFAD9A.3050304@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