From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kishon Vijay Abraham I Subject: Re: [PATCH RFC 1/4] phy: Add new Exynos5 USB 3.0 PHY driver Date: Wed, 20 Nov 2013 21:14:44 +0530 Message-ID: <528CD8EC.9050403@ti.com> References: <1383205544-32244-1-git-send-email-gautam.vivek@samsung.com> <1383205544-32244-2-git-send-email-gautam.vivek@samsung.com> <527744B2.4090303@ti.com> <030d01ced946$d6e23490$84a69db0$%debski@samsung.com> <52779D28.9000905@ti.com> <00fe01ceda0a$941957a0$bc4c06e0$%debski@samsung.com> <000001ceda17$f41c2030$dc546090$%han@samsung.com> <000101ceda1f$04ca6f20$0e5f4d60$%han@samsung.com> <000301ceda84$1d648bf0$582da3d0$%han@samsung.com> <5280BB65.5040305@ti.com> <528C7B0E.3080401@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Vivek Gautam Cc: "devicetree@vger.kernel.org" , Kamil Debski , "linux-samsung-soc@vger.kernel.org" , linux-doc@vger.kernel.org, Greg KH , Tomasz Figa , Jingoo Han , "linux-kernel@vger.kernel.org" , Felipe Balbi , Linux USB Mailing List , Vivek Gautam , Sylwester Nawrocki , Julius Werner , Kukjin Kim , "linux-arm-kernel@lists.infradead.org" List-Id: devicetree@vger.kernel.org Hi, On Wednesday 20 November 2013 03:02 PM, Vivek Gautam wrote: > On Wed, Nov 20, 2013 at 2:34 PM, Kishon Vijay Abraham I wrote: >> On Wednesday 20 November 2013 02:27 PM, Vivek Gautam wrote: >>> Hi Kishon, >>> >>> >>> On Mon, Nov 11, 2013 at 4:41 PM, Kishon Vijay Abraham I wrote: >>>> Hi, >>> sorry for the delayed response. >>> >>>> >>>> On Wednesday 06 November 2013 05:37 AM, Jingoo Han wrote: >>>>> On Wednesday, November 06, 2013 2:58 AM, Vivek Gautam wrote: >>>>>> On Tue, Nov 5, 2013 at 5:33 PM, Jingoo Han wrote: >>>>> >>>>> [.....] >>>>> >>>>>>> USB3.0 PHY consists of two blocks such as 3.0 block and 2.0 block. >>>>>>> This USB3.0 PHY can support UTMI+ and PIPE3 interface for 3.0 block >>>>>>> and 2.0 block, respectively. >>>>>>> >>>>>>> Conclusion: >>>>>>> >>>>>>> 1) USB2.0 PHY: USB2.0 HOST, USB2.0 Device >>>>>>> Base address: 0x1213 0000 >>>>>>> >>>>>>> 2) USB3.0 PHY: USB3.0 DRD (3.0 HOST & 3.0 Device) >>>>>>> Base address: 0x1210 0000 >>>>>>> 2.0 block(UTMI+) & 3.0 block(PIPE3) >>>>>> >>>>>> And this is of course the PHY used by DWC3 controller, which works at >>>>>> both High speed as well as Super Speed. >>>>>> Right ? >>>>> >>>>> Right. >>>>> >>>>> While 3.0 block(PIPE3) can be used for Super Speed, 2.0 block(UTMI+) >>>>> can be used for High speed. >>>> >>>> It should then come under *single IP muliple PHY* category similar to what >>>> Sylwester has done. >>> >>> Do you mean that i should be including PHY IDs for UTMI+ phy and PIPE3 >>> phy present in this PHY block ? >>> AFAICS the two phys (UTMI+ and PIPE3) do not really have separate >>> registers to program, and that's the reason >>> we program the entire PHY in a shot. >> >> you mean you program the same set of bits for UTMI+ and PIPE3? > > No, looking closely into PHY datasheet as well as Exynos5250 manual, i > can see that UTMI+ and PIPE3 > phys have separate bit settings. So i think we should be able to > segregate the two PHYs (UTMI+ and PIPE3). > Pardon me for my earlier observations. no problem.. > Let me clarify more with our h/w team also on this and then i will > confirm with this. sure, thanks. Cheers Kishon > >> >> Thanks >> Kishon > > >