From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
To: balbi@ti.com
Cc: Kumar Gala <galak@codeaurora.org>,
rob.herring@calxeda.com, pawel.moll@arm.com,
mark.rutland@arm.com, swarren@wwwdotorg.org,
ian.campbell@citrix.com, rob@landley.net,
gregkh@linuxfoundation.org, grant.likely@linaro.org,
idos@codeaurora.org, mgautam@codeaurora.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/3] usb: dwc3: msm: Add device tree binding information
Date: Tue, 13 Aug 2013 10:32:08 +0300 [thread overview]
Message-ID: <1376379128.2208.9.camel@iivanov-dev.int.mm-sol.com> (raw)
In-Reply-To: <20130812180438.GC27954@radagast>
Hi,
On Mon, 2013-08-12 at 13:04 -0500, Felipe Balbi wrote:
> On Fri, Aug 09, 2013 at 10:31:58AM -0500, Kumar Gala wrote:
> >
> > On Aug 9, 2013, at 4:53 AM, Ivan T. Ivanov wrote:
> >
> > > From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
> > >
> > > MSM USB3.0 core wrapper consist of USB3.0 IP (SNPS)
> >
> > probably good to spell out Synopsys rather than SNPS
>
> Synopsys (the company) has always used snps in their bindings though.
>
> > > +Required properities :
> > > +- compatible : sould be "qcom,dwc3-hsphy";
> > > +- reg : offset and length of the register set in the memory map
> > > +- clocks : phandles to clock instances of the device tree nodes
> > > +- clock-names :
> > > + "xo" : External reference clock 19 MHz
> > > + "sleep_a_clk" : Sleep clock, used when USB3 core goes into low
> > > + power mode (U3).
> > > +<supply-name>-supply : phandle to the regulator device tree node
> > > +Required "supply-name" are:
> > > + "v1p8" : 1.8v supply for HSPHY
> > > + "v3p3" : 3.3v supply for HSPHY
> > > + "vbus" : vbus supply for host mode
> > > + "vddcx" : vdd supply for HS-PHY digital circuit operation
>
> I believe these regulators belong to the PHY, not DWC3. Please write a
> PHY driver.
>
There is already usb phy drivers for these??
[PATCH v2 2/3] usb: phy: Add Qualcomm SS-USB and HS-USB drivers for DWC3 core
> > > +Required properities :
> > > +- compatible : sould be "qcom,dwc3-ssphy";
> > > +- reg : offset and length of the register set in the memory map
> > > +- clocks : phandles to clock instances of the device tree nodes
> > > +- clock-names :
> > > + "xo" : External reference clock 19 MHz
> > > + "ref_clk" : Reference clock - used in host mode.
> > > +<supply-name>-supply : phandle to the regulator device tree node
> > > +Required "supply-name" are:
> > > + "v1p8" : 1.8v supply for SS-PHY
> > > + "vddcx" : vdd supply for SS-PHY digital circuit operation
>
> likewise, these regulators should be moved to the PHY driver.
>
> > > +Required properties :
> > > +- compatible : should be "qcom,dwc3"
> > > +- reg : offset and length of the register set in the memory map
> > > + offset and length of the TCSR register for routing USB
> > > + signals to either picoPHY0 or picoPHY1.
> > > +- clocks : phandles to clock instances of the device tree nodes
> > > +- clock-names :
> > > + "core_clk" : Master/Core clock, have to be >= 125 MHz for SS
> > > + operation and >= 60MHz for HS operation
> > > + "iface_clk" : System bus AXI clock
> > > + "sleep_clk" : Sleep clock, used when USB3 core goes into low
> > > + power mode (U3).
> > > + "utmi_clk" : Generated by HS-PHY. Used to clock the low power
> > > + parts of thr HS Link layer.
> > > +
> > > +Optional properties :
> > > +- gdsc-supply : phandle to the globally distributed switch controller
> > > + regulator node to the USB controller.
> > > +
> > > +Sub nodes:
> > > +- Sub node for "DWC3 USB3 controller".
> > > + This sub node is required property for device node. The properties
> > > + of this subnode are specified in dwc3.txt.
> >
> > Is tx-fifo-resize required for qcom,dwc3? if so we should call that
> > out in the binding.
>
> AFAICT that's only needed for OMAP5 ES1.0. Unless Qualcomm also screwed
> up default TX FIFO sizes :-p
Or it is intentional? :-) Look at [1] dwc3@f9200000
Ivan
[1] https://www.codeaurora.org/cgit/quic/la/kernel/msm/tree/arch/arm/boot/dts/apq8084.dtsi?h=msm-3.4
>
next prev parent reply other threads:[~2013-08-13 7:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 9:53 [RFC PATCH v2 0/3] DWC3 USB support for Qualcomm platform Ivan T. Ivanov
2013-08-09 9:53 ` [RFC PATCH v2 1/3] usb: dwc3: msm: Add device tree binding information Ivan T. Ivanov
[not found] ` <169628C9-00BA-4E58-BF65-7B180E6BE4ED@codeaurora.org>
2013-08-12 18:04 ` Felipe Balbi
2013-08-12 18:49 ` Kumar Gala
2013-08-13 7:32 ` Ivan T. Ivanov [this message]
2013-08-13 7:21 ` Ivan T. Ivanov
2013-08-13 19:57 ` Stephen Warren
2013-08-14 7:18 ` Ivan T. Ivanov
2013-08-09 9:53 ` [RFC PATCH v2 2/3] usb: phy: Add Qualcomm SS-USB and HS-USB drivers for DWC3 core Ivan T. Ivanov
2013-08-09 9:53 ` [RFC PATCH v2 3/3] usb: dwc3: Add Qualcomm DWC3 glue layer driver Ivan T. Ivanov
2013-08-09 13:32 ` Felipe Balbi
2013-08-09 15:16 ` 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=1376379128.2208.9.camel@iivanov-dev.int.mm-sol.com \
--to=iivanov@mm-sol.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=mark.rutland@arm.com \
--cc=mgautam@codeaurora.org \
--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).