From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
To: Pawel Moll <pawel.moll@arm.com>
Cc: Kumar Gala <galak@codeaurora.org>, "balbi@ti.com" <balbi@ti.com>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Mark Rutland <Mark.Rutland@arm.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"rob@landley.net" <rob@landley.net>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"idos@codeaurora.org" <idos@codeaurora.org>,
"mgautam@codeaurora.org" <mgautam@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
Paul Zimmerman <paul.zimmerman@synopsys.com>
Subject: Re: [PATCH v4 2/3] usb: phy: Add Qualcomm SS-USB and HS-USB drivers for DWC3 core
Date: Wed, 21 Aug 2013 16:06:04 +0300 [thread overview]
Message-ID: <1377090364.15070.13.camel@iivanov-dev.int.mm-sol.com> (raw)
In-Reply-To: <1377018092.31445.42.camel@hornet>
On Tue, 2013-08-20 at 18:01 +0100, Pawel Moll wrote:
> On Tue, 2013-08-20 at 16:06 +0100, Pawel Moll wrote:
> > On Tue, 2013-08-20 at 16:01 +0100, Kumar Gala wrote:
> > > On Aug 20, 2013, at 9:54 AM, Ivan T. Ivanov wrote:
> > >
> > > >
> > > > Hi,
> > > >
> > > > On Tue, 2013-08-20 at 09:33 -0500, Felipe Balbi wrote:
> > > >> On Tue, Aug 20, 2013 at 05:09:11PM +0300, Ivan T. Ivanov wrote:
> > > >>> Hi,
> > > >>>
> > > >>> On Tue, 2013-08-20 at 08:37 -0500, Felipe Balbi wrote:
> > > >>>> Hi,
> > > >>>>
> > > >>>> On Tue, Aug 20, 2013 at 04:32:23PM +0300, Ivan T. Ivanov wrote:
> > > >>>>>> On Tue, Aug 20, 2013 at 12:56:04PM +0300, Ivan T. Ivanov wrote:
> > > >>>>>>> From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
> > > >>>>>>>
> > > >>>>>>> These drivers handles control and configuration of the HS
> > > >>>>>>> and SS USB PHY transceivers. They are part of the driver
> > > >>>>>>> which manage Synopsys DesignWare USB3 controller stack
> > > >>>>>>> inside Qualcomm SoC's.
> > > >>>>>>>
> > > >>>>>>> Signed-off-by: Ivan T. Ivanov <iivanov@mm-sol.com>
> > > >>>>>>> ---
> > > >>>>>>> drivers/usb/phy/Kconfig | 11 ++
> > > >>>>>>> drivers/usb/phy/Makefile | 2 +
> > > >>>>>>> drivers/usb/phy/phy-msm-dwc3-hs.c | 327 ++++++++++++++++++++++++++++++++
> > > >>>>>>> drivers/usb/phy/phy-msm-dwc3-ss.c | 374 +++++++++++++++++++++++++++++++++++++
> > > >>>>>>
> > > >>>>>> please rename these PHY drivers, they have nothing to do with DWC3. PHYs
> > > >>>>>> don't care about the USB controller.
> > > >>>>>
> > > >>>>> I think they are SNPS DesignWare PHY's, additionally
> > > >>>>> wrapped with Qualcomm logic. I could substitute "dwc3"
> > > >>>>> with just "dw", which will be more correct.
> > > >>>>
> > > >>>> alright, thank you. Let's add Paul to the loop since he might have very
> > > >>>> good insight in the synopsys PHYs.
> > > >>>>
> > > >>>> mental note: if any other platform shows up with Synopsys PHY, ask them
> > > >>>> to use this driver instead :-)
> > > >>>
> > > >>> I really doubt that this will bi possible. Control of the PHY's is
> > > >>> not directly trough ULPI, UTMI or PIPE3 interfaces, but trough
> > > >>> QSCRATCH registers, which of course is highly Qualcomm specific.
> > > >>
> > > >> isn't it a memory mapped IP ? doesn't synopsys provide their own set of
> > > >> registers ?
> > > >
> > > > From what I see it is not directly mapped. How QSCRATCH write and
> > > > reads transactions are translated to DW IP is unclear to me.
> > >
> > >
> > > I think the question is how does SW access them?
> >
> > I afraid the answer may be: "it depends on the SOC". In my past I had to
> > initialize a (SATA) PHY by implementing a software JTAG state machine,
> > as the PHY's registers were not memory mapped *at all*. And the IP
> > itself came from Synopsys, Cadence or yet another EDA company...
>
> Having said all that... If the PHY's spec at least defined layout of the
> registers in question and driver was using regmap API to talk to the
> device (initially regmap-mmio), it has some chances to become universal.
> The SOCs designed like "my" one would have to provide a custom regmap
> implementation.
Sound reasonable. Unfortunately I don't have PHY's IP spec.
Regards,
Ivan
>
> Paweł
>
next prev parent reply other threads:[~2013-08-21 13:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 9:56 [PATCH v4 0/3] DWC3 USB support for Qualcomm platform Ivan T. Ivanov
2013-08-20 9:56 ` [PATCH v4 1/3] usb: dwc3: msm: Add device tree binding information Ivan T. Ivanov
2013-09-23 19:31 ` Felipe Balbi
2013-09-26 9:46 ` Mark Rutland
[not found] ` <20130926094618.GD2411-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-10-01 11:47 ` Ivan T. Ivanov
2013-10-01 11:49 ` Ivan T. Ivanov
2013-08-20 9:56 ` [PATCH v4 2/3] usb: phy: Add Qualcomm SS-USB and HS-USB drivers for DWC3 core Ivan T. Ivanov
2013-08-20 12:29 ` Felipe Balbi
2013-08-20 13:32 ` Ivan T. Ivanov
2013-08-20 13:37 ` Felipe Balbi
2013-08-20 14:09 ` Ivan T. Ivanov
2013-08-20 14:33 ` Felipe Balbi
2013-08-20 14:54 ` Ivan T. Ivanov
2013-08-20 15:01 ` Kumar Gala
2013-08-20 15:06 ` Pawel Moll
2013-08-20 17:01 ` Pawel Moll
2013-08-21 13:06 ` Ivan T. Ivanov [this message]
[not found] ` <68B25A45-443C-4CC0-9933-80A3D290B557@codeaurora.org>
2013-08-22 20:41 ` Felipe Balbi
2013-08-29 17:28 ` Ivan T. Ivanov
2013-08-20 15:26 ` Ivan T. Ivanov
2013-08-22 21:24 ` Paul Zimmerman
2013-08-27 19:58 ` Felipe Balbi
2013-08-20 9:56 ` [PATCH v4 3/3] usb: dwc3: Add Qualcomm DWC3 glue layer driver Ivan T. Ivanov
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=1377090364.15070.13.camel@iivanov-dev.int.mm-sol.com \
--to=iivanov@mm-sol.com \
--cc=Mark.Rutland@arm.com \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=ian.campbell@citrix.com \
--cc=idos@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgautam@codeaurora.org \
--cc=paul.zimmerman@synopsys.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=swarren@wwwdotorg.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).