linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jg1.han@samsung.com (Jingoo Han)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 1/4] phy: Add new Exynos5 USB 3.0 PHY driver
Date: Tue, 05 Nov 2013 20:12:45 +0900	[thread overview]
Message-ID: <000001ceda17$f41c2030$dc546090$%han@samsung.com> (raw)
In-Reply-To: <00fe01ceda0a$941957a0$bc4c06e0$%debski@samsung.com>

On Tuesday, November 05, 2013 6:37 PM, Kamil Debski wrote:
> On Tuesday, November 05, 2013 8:20 AM, Vivek Gautam wrote:
> > On Mon, Nov 4, 2013 at 6:42 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
> > > On Monday 04 November 2013 03:45 PM, Kamil Debski wrote:
> > >> On Monday, November 04, 2013 7:55 AM, Kishon Vijay Abraham I wrote:
> > >>> On Thursday 31 October 2013 01:15 PM, 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.
> > >>>
> > >>>
> > >>> In Exynos, you have a single IP that supports both USB3 and USB2
> > PHY
> > >>> right? I think that needs to be mentioned here.
> > >>
> > >>
> > >> As far as I know the IP is different.
> > >
> > >
> > > Ok. Sometime back Vivek was mentioning about a single IP for both
> > USB3
> > > and USB2. Thought it should be this driver. Anyway thanks for the
> > clarification.
> >
> > Right Kishon, I had mentioned that Exynos5's dwc3 controller have a
> > single IP for USB2 and USB3 phy.
> > From what i see, on exynos5 systems the dwc3 controller uses a combo of
> > usb 2 (utmi+) and usb 3 (pipe 3) phy (with base address starting
> > 0x12100000).
> >
> > Kamil, Tomasz,
> >
> > Please correct me if i am wrong.
> 
> I have the Exynos 5250 documentation and I found two phy register ranges:
> 1) USB 2.0 PHY having the base address of 0x1213 0000
> 	Chapter 33. USB 2.0 Host Controller
> 	Subchapter 33.5.2 Phy Control Register p. 1696
> 	First register's description is
> 	"USB2.0 phy control register"
> 2) USB 3.0 PHY (I guess) with the base address 0x1210 0000
> 	Chapter 35. USB 3.0 DRD Controller
> 	Subchapter 35.4.6 PHY Control Register p. 1872
> 
> Jingoo, could you comment on the above? You may know more than we do :)

Hi Kamil,

Thank you for trusting me. :-)
I just asked my validation engineer about 5250 USB PHY.
As I know, she has the best knowledge about Samsung SoC USB hardware.
She said that there are 2 PHY controllers such as USB 2.0 PHY, USB 3.0 PHY.

  1) USB2.0 PHY: USB2.0 HOST, USB2.0 Device
  2) USB3.0 PHY: USB3.0 DRD (3.0 HOST & 3.0 Device)

> In addition, I have a question to you Vivek - does your USB 3.0
> PHY support both host and device?

According to her, USB3.0 PHY can support both 3.0 Host and 3.0 Device.
Thank you.

Best regards,
Jingoo Han

  reply	other threads:[~2013-11-05 11:12 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31  7:45 [PATCH RFC 0/4] Add Exynos5 USB 3.0 phy driver based on generic PHY framework Vivek Gautam
2013-10-31  7:45 ` [PATCH RFC 1/4] phy: Add new Exynos5 USB 3.0 PHY driver Vivek Gautam
2013-11-04  6:54   ` Kishon Vijay Abraham I
2013-11-04 10:15     ` Kamil Debski
2013-11-04 13:12       ` Kishon Vijay Abraham I
2013-11-05  7:20         ` Vivek Gautam
2013-11-05  9:34           ` Tomasz Figa
2013-11-05  9:36           ` Kamil Debski
2013-11-05 11:12             ` Jingoo Han [this message]
2013-11-05 12:03               ` Jingoo Han
2013-11-05 17:58                 ` Vivek Gautam
2013-11-06  0:07                   ` Jingoo Han
2013-11-11 11:11                     ` Kishon Vijay Abraham I
2013-11-20  8:57                       ` Vivek Gautam
2013-11-20  9:04                         ` Kishon Vijay Abraham I
2013-11-20  9:32                           ` Vivek Gautam
2013-11-20 15:44                             ` Kishon Vijay Abraham I
2013-12-04 14:28                               ` Kishon Vijay Abraham I
2013-12-05  8:14                                 ` Vivek Gautam
2013-12-24 17:45                                   ` Kishon Vijay Abraham I
2013-12-30  9:43                                     ` Vivek Gautam
2014-01-07  9:49                                       ` Kishon Vijay Abraham I
2014-01-07 11:03                                         ` Vivek Gautam
2014-01-20 13:45                                           ` Vivek Gautam
2013-11-05 17:56             ` Vivek Gautam
2013-11-04 12:26     ` Tomasz Figa
2013-11-04 13:09       ` Kishon Vijay Abraham I
     [not found]       ` <CAFp+6iG5SAe5h0-RRsBuAhtWO_NBW6G=7jQeObd4Y2BQGaRHyA@mail.gmail.com>
2013-11-05  7:12         ` Vivek Gautam
2013-11-10 14:08   ` Tomasz Figa
2013-11-20  8:44     ` Vivek Gautam
2013-11-20  8:55       ` Vivek Gautam
2013-11-21 12:26   ` Yuvaraj Cd
2013-10-31  7:45 ` [PATCH 2/4] dt: exynos5250: Enable support for generic USB 3.0 phy Vivek Gautam
2013-11-10 14:54   ` Tomasz Figa
2013-10-31  7:45 ` [PATCH 3/4] dt: exynos5420: Enable support for USB 3.0 PHY controller Vivek Gautam
2013-10-31  7:45 ` [PATCH 4/4] dt: exynos5420: Enable support for DWC3 controller 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='000001ceda17$f41c2030$dc546090$%han@samsung.com' \
    --to=jg1.han@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).