From: Vladimir Zapolskiy <vz@mleia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v6 5/5] usb: lpc32xx: add host USB driver
Date: Thu, 13 Aug 2015 18:03:07 +0300 [thread overview]
Message-ID: <55CCB1AB.7040606@mleia.com> (raw)
In-Reply-To: <4F172219764C784B84C2C1FF44E7DFB103011952@003FCH1MPN2-041.003f.mgd2.msft.net>
On 13.08.2015 14:55, LEMIEUX, SYLVAIN wrote:
>
>> -----Original Message-----
>> From: Vladimir Zapolskiy [mailto:vz at mleia.com]
>> Sent: 12-Aug-15 8:05 PM
>>
>> Hi Sylvain,
>>
>> On 12.08.2015 23:00, LEMIEUX, SYLVAIN wrote:
>>> Hi Vladimir and Marek,
>>>
>>>> -----Original Message-----
>>>> From: Vladimir Zapolskiy [mailto:vz at mleia.com]
>>>> Sent: 12-Aug-15 1:55 PM
>>>>
>>>> Hi Sylvain,
>>>>
>>>> On 10.08.2015 15:16, slemieux.tyco at gmail.com wrote:
>>>>> From: Sylvain Lemieux <slemieux@tycoint.com>
>>>>>
>>>>> Incorporate USB driver from legacy LPCLinux NXP BSP.
>>>>> The files taken from the legacy patch are:
>>>>> - lpc32xx USB driver
>>>>> - lpc3250 header file USB registers definition.
>>>>>
>>>>> The legacy driver was updated and clean-up as part of the integration with the latest u-boot.
>>>>>
>>>>> Signed-off-by: Sylvain Lemieux <slemieux@tycoint.com>
>>>>> ---
>>
>> [snip]
>>
>>>>> + }
>>>>> +
>>>>> + /* Configure ISP1301 */
>>>>> + isp1301_configure();
>>>>
>>>> Not sure if there are any LPC32xx boards with USB host/device, but
>>>> without ISP1301 phy. Let it be here until such a board emerges, if Marek
>>>> does not object.
>>>>
>>>> In general I wonder, won't drivers/usb/phy/ be a better place for this
>>>> driver or bigger part of it?
>>>
>>> The Embedded Artists LPC3250 OEM Board is having the USB with the ISP1301;
>>> http://www.embeddedartists.com/products/kits/lpc3250_kit.php
>>> The legacy NXP LPC32xx BSP included board support files for it.
>>>
>>
>> it seems to be a usual design pattern, my devkit3250 board also has
>> ISP1301 phy. The question is if fusion of a particular external phy
>> device driver and a particular host device driver are permitted in form
>> of a host driver only.
>>
>> This is a question in area of device driver(s) maintenance, therefore
>> Marek should rule it. For me as a user I'm satisfied with the approach,
>> when on-SoC host device and external phy device share one driver for
>> both. Just when an LPC32xx powered board with USB emerges without
>> ISP1301 phy or other way round ISP1301 phy is used in junction with
>> another host/device, this time the driver will be split.
>>
> The maintainer, Marek, previously ack the patch;
> https://www.mail-archive.com/u-boot at lists.denx.de/msg180934.html
> I am assuming it is OK to keep the current approach.
>
> I will add your tested, as per this message listed below and the ack from
> Marek when I submit revision 7, later today.
> https://www.mail-archive.com/u-boot at lists.denx.de/msg180934.html
>
Sure, thank you.
--
With best wishes,
Vladimir
prev parent reply other threads:[~2015-08-13 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 12:16 [U-Boot] [PATCH v6 5/5] usb: lpc32xx: add host USB driver slemieux.tyco at gmail.com
2015-08-10 12:23 ` Marek Vasut
2015-08-10 13:15 ` LEMIEUX, SYLVAIN
2015-08-12 17:55 ` Vladimir Zapolskiy
2015-08-12 19:41 ` Marek Vasut
2015-08-12 19:47 ` LEMIEUX, SYLVAIN
2015-08-12 21:35 ` Vladimir Zapolskiy
2015-08-12 22:10 ` Marek Vasut
2015-08-12 20:00 ` LEMIEUX, SYLVAIN
2015-08-13 0:04 ` Vladimir Zapolskiy
2015-08-13 11:55 ` LEMIEUX, SYLVAIN
2015-08-13 15:03 ` Vladimir Zapolskiy [this message]
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=55CCB1AB.7040606@mleia.com \
--to=vz@mleia.com \
--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