From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v7 3/3] usb: dwc3: qcom: Add device tree binding
Date: Tue, 1 Jul 2014 00:04:35 -0500 [thread overview]
Message-ID: <CAL_JsqJTO4htxHMVtMG6mGLmgRtQ7igE1OCX_jXM4xabN76ntg@mail.gmail.com> (raw)
In-Reply-To: <1404144233-17222-4-git-send-email-agross@codeaurora.org>
On Mon, Jun 30, 2014 at 11:03 AM, Andy Gross <agross@codeaurora.org> wrote:
> From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Please copy the right lists and maintainers.
>
> QCOM USB3.0 core wrapper consist of USB3.0 IP from Synopsys
> (SNPS) and HS, SS PHY's control and configuration registers.
>
> It could operate in device mode (SS, HS, FS) and host
> mode (SS, HS, FS, LS).
>
> Signed-off-by: Ivan T. Ivanov <iivanov@mm-sol.com>
> Signed-off-by: Andy Gross <agross@codeaurora.org>
> ---
> .../devicetree/bindings/usb/qcom,dwc3.txt | 104 ++++++++++++++++++++
> 1 file changed, 104 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/usb/qcom,dwc3.txt
>
> diff --git a/Documentation/devicetree/bindings/usb/qcom,dwc3.txt b/Documentation/devicetree/bindings/usb/qcom,dwc3.txt
> new file mode 100644
> index 0000000..105b6b7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/qcom,dwc3.txt
> @@ -0,0 +1,104 @@
> +Qualcomm SuperSpeed DWC3 USB SoC controller
> +
> +
> +QCOM DWC3 Highspeed USB PHY
> +========================
> +Required properities:
> +- compatible: should contain "qcom,dwc3-hsphy";
> +- reg: offset and length of the register set in the memory map
> +- clocks: A list of phandle + clock-specifier pairs for the
> + clocks listed in clock-names
> +- clock-names: Should contain the following:
> + "utmi" UTMI clock
> +- v1p8-supply: phandle to the regulator for the 1.8v supply to HSPHY.
> +- v3p3-supply: phandle to the regulator for the 3.3v supply to HSPHY.
> +- vbus-supply: phandle to the regulator for the vbus supply for host
> + mode.
> +- vddcx-supply: phandle to the regulator for the vdd supply for HSPHY
> + digital circuit operation.
> +
> +Optional clocks:
> + "xo" External reference clock
> +
> +
> +QCOM DWC3 Superspeed USB PHY
> +=========================
> +Required properities:
> +- compatible: should contain "qcom,dwc3-ssphy";
> +- reg: offset and length of the register set in the memory map
> +- clocks: A list of phandle + clock-specifier pairs for the
> + clocks listed in clock-names
> +- clock-names: Should contain the following:
> + "ref" Reference clock used in host mode.
> +- v1p8-supply: phandle to the regulator for the 1.8v supply to HSPHY.
> +- vddcx-supply: phandle to the regulator for the vdd supply for HSPHY
> + digital circuit operation.
> +
> +Optional clocks:
> + "xo" External reference clock
> +
> +QCOM DWC3 controller wrapper
> +===========================
> +Required properties:
> +- compatible: should contain "qcom,dwc3"
> +- clocks: A list of phandle + clock-specifier pairs for the
> + clocks listed in clock-names
> +- clock-names: Should contain the following:
> + "core" Master/Core clock, have to be >= 125 MHz for SS
> + operation and >= 60MHz for HS operation
> +
> +Optional clocks:
> + "iface" System bus AXI clock. Not present on all platforms
Really?, some platforms have a clockless bus?
> + "sleep" Sleep clock, used when USB3 core goes into low
> + power mode (U3).
> +
> +Optional regulator:
> +- gdsc-supply: phandle to the regulator from globally distributed
> + switch controller
The name should reflect the name of the input, not the source.
> +
> +Required child node:
> +A child node must exist to represent the core DWC3 IP block. The name of
> +the node is not important. The content of the node is defined in dwc3.txt.
> +
> +Example device nodes:
> +
> + hs_phy_0: phy at 110f8800 {
> + compatible = "qcom,dwc3-hsphy";
> + reg = <0x110f8800 0x30>;
> + clocks = <&gcc USB30_0_UTMI_CLK>;
> + clock-names = "utmi";
> +
> + status = "disabled";
> + };
> +
> + ss_phy_0: phy at 110f8830 {
> + compatible = "qcom,dwc3-ssphy";
> + reg = <0x110f8830 0x30>;
> +
> + clocks = <&gcc USB30_0_MASTER_CLK>;
> + clock-names = "ref";
> +
> + status = "disabled";
> + };
> +
> + usb3_0: usb30 at 0 {
> + compatible = "qcom,dwc3";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + clocks = <&gcc USB30_0_MASTER_CLK>;
> + clock-names = "core";
> +
> + ranges;
> +
> + status = "disabled";
> +
> + dwc3 at 11000000 {
> + compatible = "snps,dwc3";
This sub-node is just wrong. Why can't you have a single node with '
"qcom,dwc3", "snps,dwc3" ' for the compatible property? All you are
adding here is clocks. Does the Synopsys block have no clocks?
I guess this is copied from other broken dwc3 bindings... That doesn't
mean you have to copy it.
Rob
next prev parent reply other threads:[~2014-07-01 5:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 16:03 [Patch v7 0/3] DWC3 USB support for Qualcomm platform Andy Gross
2014-06-30 16:03 ` [Patch v7 1/3] usb: dwc3: Add Qualcomm DWC3 glue layer driver Andy Gross
2014-06-30 16:52 ` Felipe Balbi
2014-07-18 2:10 ` Jingoo Han
2014-06-30 16:03 ` [Patch v7 2/3] usb: phy: Add Qualcomm DWC3 HS/SS PHY drivers Andy Gross
2014-06-30 17:00 ` Felipe Balbi
[not found] ` <CA+neC=McWS8=iSi2XShJyvc85Aw4PSmF-osNpVgJv42d9or1WQ@mail.gmail.com>
2014-07-17 10:30 ` kiran.padwal at smartplayin.com
2014-07-17 18:28 ` Andy Gross
2014-06-30 16:03 ` [Patch v7 3/3] usb: dwc3: qcom: Add device tree binding Andy Gross
2014-06-30 17:37 ` Kumar Gala
2014-07-01 5:04 ` Rob Herring [this message]
2014-07-01 18:01 ` Andy Gross
2014-07-01 19:47 ` Rob Herring
2014-07-02 8:43 ` Ivan T. Ivanov
2014-07-02 12:48 ` Arnd Bergmann
2014-07-02 15:54 ` Felipe Balbi
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=CAL_JsqJTO4htxHMVtMG6mGLmgRtQ7igE1OCX_jXM4xabN76ntg@mail.gmail.com \
--to=robherring2@gmail.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).