From: Kishon Vijay Abraham I <kishon@ti.com>
To: Tomasz Figa <t.figa@samsung.com>,
Vivek Gautam <gautam.vivek@samsung.com>,
linux-usb@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, gregkh@linuxfoundation.org,
kgene.kim@samsung.com, balbi@ti.com, k.debski@samsung.com,
s.nawrocki@samsung.com, jwerner@chromium.org,
jg1.han@samsung.com
Subject: Re: [PATCH v3] phy: Add new Exynos5 USB 3.0 PHY driver
Date: Mon, 10 Feb 2014 13:57:37 +0530 [thread overview]
Message-ID: <52F88D79.9040203@ti.com> (raw)
In-Reply-To: <52F39710.80101@samsung.com>
Hi,
On Thursday 06 February 2014 07:37 PM, Tomasz Figa wrote:
> Hi Vivek,
>
> This patch is just adding the PHY driver. I would also like to look at some
> users of it, to see how this works when put together.
>
> For now, please see my comments inline.
>
> On 20.01.2014 14:42, Vivek Gautam wrote:
>> Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs.
>> The new driver uses the generic PHY framework and will interact
>> with DWC3 controller present on Exynos5 series of SoCs.
>> Thereby, removing old phy-samsung-usb3 driver and related code
>> used untill now which was based on usb/phy framework.
>>
>> Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com>
>> ---
>>
>> Changes from v2:
>> 1) Added support for multiple PHYs (UTMI+ and PIPE3) and
>> related changes in the driver structuring.
>
> I'm a bit skeptical about this separation. Can the PHY operate with just the
> UTMI+ or PIPE3 part enabled alone without the other? Can any PHY consumer
> operate this way?
Theoretically yes. If the USB controller should operate only in high-speed
mode, the PIPE3 part is not required at all. However for super speed mode both
PIPE3 part and UTMI part should be enabled. Maybe it doesn't work that way with
all SoCs because of some HW bug.
>
> Introducing separation of something that can't exist alone doesn't add any
> value, but instead makes things more difficult to work with. Of course, it's
IMO separating it into different parts adds more clarity to the driver.
Thanks
Kishon
next prev parent reply other threads:[~2014-02-10 8:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1386151747-3209-2-git-send-email-gautam.vivek@samsung.com>
2014-01-20 13:42 ` [PATCH v3] phy: Add new Exynos5 USB 3.0 PHY driver Vivek Gautam
2014-01-21 7:46 ` Vivek Gautam
2014-01-27 8:57 ` Kishon Vijay Abraham I
[not found] ` <52E61F63.1090200-l0cyMroinI0@public.gmane.org>
2014-01-30 4:19 ` Vivek Gautam
2014-01-30 6:18 ` Kishon Vijay Abraham I
2014-01-30 7:33 ` Vivek Gautam
2014-02-06 14:07 ` Tomasz Figa
2014-02-10 8:27 ` Kishon Vijay Abraham I [this message]
2014-02-14 13:53 ` Vivek Gautam
[not found] ` <CAFp+6iFYoN1w_BX7mMEa-Xx5ADaPTTKeDzjsSbQmwVKdSEsmOw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-14 15:47 ` Tomasz Figa
2014-02-17 10:01 ` Vivek Gautam
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=52F88D79.9040203@ti.com \
--to=kishon@ti.com \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=gautam.vivek@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=jg1.han@samsung.com \
--cc=jwerner@chromium.org \
--cc=k.debski@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=t.figa@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).