Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp69932ybl; Wed, 11 Dec 2019 14:11:14 -0800 (PST) X-Google-Smtp-Source: APXvYqwwV/7y0NpQNxmGrcsJyVXk4pSEKa7ABxNgtKlA3BJ8aRlg8JXKtdJgN7wAhx4pMNg7n/bV X-Received: by 2002:a9d:4706:: with SMTP id a6mr3919771otf.331.1576102274830; Wed, 11 Dec 2019 14:11:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576102274; cv=none; d=google.com; s=arc-20160816; b=BElxuGq7hF061LNJviwaRjQnX7D29J+J3TgJR6UcyfQxM2f0M1Jr4bzw+KexrCwU2D OVDwzF5y1V+uFjHTYRz7LU99WvFyimNPeZ6YvXzyhUMoTjejh0M9FQr1xyv9zFB1o6IY YXSAFYRdWlnoKRxiD2dhql80nWYA1iTZFha2Z3t0K9R3zdlY8T0MoU03GUThXUnsjb4u YhFoHdyuNPr2DEai9Emtt1frj9AP1nVC7WNI2KJm5UxahhOIqA30EPZJnaOFBc7EdE9W EyPDxgwxQl96IOa9OWhUMkruebl8zUThSnCW3GmdMc0tW8nDWsJ4tEUUQOpRcaXcTfIq PRqg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=c/DgPdEIcvo7aTnadeKABBNpooev54ppXStm5BO3aXU=; b=sbC16xLO+2nyUblGTZn0nRX8CYVu1osIjCRWFWyD6YzVsSsU8IbDTJosX3het5vRUt 60Ov8zNUs0LLR/qe/jFsXyCwsAuknN0lvBWTWQlVqgGNOlH/UpB3prSGEDFov7WiJewB 62r8qyJD8fEhzzz8TeOIlDtF23Yz+pYyKbUpUfY9YmuCF7zgkYLtW2Anu88bGubEZuns D4nH8huJr5aOKFYyMGl6sGi7zQ2e/7BIRpBXbvRIrq4Y/GnL1ytu1fWMS+GuZw5xQ20p e6tnBTPcZk6Y+rAAH6DdimoqeQ1GjSOoU/+jLWIccT3he5ZIvIwrNfTBDSYYzZG2vcmP 2Rdg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=C4caIpwX; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v14si1762419oto.127.2019.12.11.14.10.59; Wed, 11 Dec 2019 14:11:14 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=C4caIpwX; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726771AbfLKWKT (ORCPT + 99 others); Wed, 11 Dec 2019 17:10:19 -0500 Received: from mail-il1-f171.google.com ([209.85.166.171]:46528 "EHLO mail-il1-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726368AbfLKWKS (ORCPT ); Wed, 11 Dec 2019 17:10:18 -0500 Received: by mail-il1-f171.google.com with SMTP id t17so192695ilm.13 for ; Wed, 11 Dec 2019 14:10:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=c/DgPdEIcvo7aTnadeKABBNpooev54ppXStm5BO3aXU=; b=C4caIpwXZtBlXDFiKAdSnRs6P5/Sk1QTPSUjoFO9pJAmiyEOMWQUzfGDIbefLk1ppj 9oO/Y+rJVCKJoLpJjjTLVqhQxbqCVrR+eQ+0m9JX94XkrVtb2qR5ZC8lvwT7qroIpSvX +PfU9ePCU5kfZViY/BXDXikFX6FpqIndz1IcQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=c/DgPdEIcvo7aTnadeKABBNpooev54ppXStm5BO3aXU=; b=Zv4wiLhC2BHavv19UPhHhUdu1Na0Lo8+aPoHYaSRz7my2s+MYYY0li4NmAaF/biCPT UN+U5biELPRNkjG/9FUzlvMQpXYDGda3CC5GH5Evm+4JRHTrkYcyGo7wrZ87KweY1kQd 7w+nJrBRNtJOCsZ22b6qGTZll0BxkONNehq5mTtsaftXNb/CmVUlnpvSNHyzlIAFaqA5 i/wJbDi6hQA631uz05cvqB4bWsip+50dN9nwJYuIciXF2OA0oUoyL1LN30r6X3/ZwPqu sqczzIc8RSqc873z0K5GflRo8K2LTzTnzkR3qgUUl3PsAb+9DrPs8y8A3cDNQKxgl/jM DZmQ== X-Gm-Message-State: APjAAAUH1mMvzfyo9lNjFigu+/d5qX+w8yLtk8JsFICg5/UVQEVvNHy2 kxuyQFxzFPV5GuEwM/iqhvd+GQY8EdM= X-Received: by 2002:a05:6e02:5c3:: with SMTP id l3mr3503463ils.260.1576102216931; Wed, 11 Dec 2019 14:10:16 -0800 (PST) Received: from mail-il1-f174.google.com (mail-il1-f174.google.com. [209.85.166.174]) by smtp.gmail.com with ESMTPSA id e5sm1080783ilq.77.2019.12.11.14.10.15 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 11 Dec 2019 14:10:16 -0800 (PST) Received: by mail-il1-f174.google.com with SMTP id w13so255752ilo.1 for ; Wed, 11 Dec 2019 14:10:15 -0800 (PST) X-Received: by 2002:a92:d581:: with SMTP id a1mr4935854iln.218.1576102215159; Wed, 11 Dec 2019 14:10:15 -0800 (PST) MIME-Version: 1.0 References: <1574940787-1004-1-git-send-email-sanm@codeaurora.org> <1574940787-1004-3-git-send-email-sanm@codeaurora.org> In-Reply-To: <1574940787-1004-3-git-send-email-sanm@codeaurora.org> From: Doug Anderson Date: Wed, 11 Dec 2019 14:10:02 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 2/3] dt-bindings: usb: qcom,dwc3: Convert USB DWC3 bindings To: Sandeep Maheswaram Cc: Andy Gross , Bjorn Andersson , Greg Kroah-Hartman , Rob Herring , Mark Rutland , Felipe Balbi , Stephen Boyd , linux-arm-msm , linux-usb@vger.kernel.org, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , LKML , Manu Gautam Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, This is my first time reviewing a yaml conversion, so if I say something that seems wrong it might very well be. That being said... On Thu, Nov 28, 2019 at 3:33 AM Sandeep Maheswaram wrote: > > diff --git a/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml > new file mode 100644 > index 0000000..48ff9c5 > --- /dev/null > +++ b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml > @@ -0,0 +1,155 @@ > +# SPDX-License-Identifier: GPL-2.0-only > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/usb/qcom,dwc3.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Qualcomm SuperSpeed DWC3 USB SoC controller > + > +maintainers: > + - Manu Gautam Really weird that you list him as the maintainer but don't CC him on this email. Is he still the maintainer? > +properties: > + compatible: > + items: > + - enum: > + - qcom,msm8996-dwc3 > + - qcom,msm8998-dwc3 > + - qcom,sdm845-dwc3 > + - const: qcom,dwc3 > + > + reg: > + description: Offset and length of register set for QSCRATCH wrapper > + maxItems: 1 > + > + power-domains: > + description: specifies a phandle to PM domain provider node > + maxItems: 1 > + > + clocks: > + description: > + A list of phandle and clock-specifier pairs for the clocks > + listed in clock-names. > + maxItems: 5 Add: "minItems: 3" > + clock-names: > + maxItems: 5 Remove "maxItems: 5". Having maxItems exactly equal to the number of items listed is the default. Add "minItems: 3" > + items: > + #Master/Core clock, have to be >= 125 MHz for SS operation > + # and >= 60MHz for HS operation Rather than add these as comments, I think you can add them as descriptions up under the "clocks" section. Look at "Documentation/devicetree/bindings/net/amlogic,meson-dwmac.yaml" as an example. Then you can also get rid of "maxItems: 5" in the "clocks" section". > + - const: core > + #Mock utmi clock needed for ITP/SOF generation in host mode. > + #Its frequency should be 19.2MHz. > + - const: mock_utmi > + #Sleep clock, used for wakeup when USB3 core goes into low power mode (U3). > + - const: sleep > + #Optional:System bus AXI clock.Not present on "qcom,msm8996-dwc3" compatible. spaces after a period. Also: once you move this up to be in the "description" of the clock node you can get rid of "Optional:" since it will be implied by "minItems: 3". > + - const: iface > + #Optional:System Config NOC clock.Not present on "qcom,msm8996-dwc3" compatible. > + - const: cfg_noc > + > + assigned-clocks: > + description: > + Should be MOCK_UTMI_CLK and MASTER_CLK > + maxItems: 2 Instead, maybe: assigned-clocks: items: - description: Phandle to MOCK_UTMI_CLK. - description: Phandle to MASTER_CLK > + assigned-clock-rates: > + description: > + Should be 19.2Mhz (192000000) for MOCK_UTMI_CLK > + >=125Mhz (125000000) for MASTER_CLK in SS mode > + >=60Mhz (60000000) for MASTER_CLK in HS mode > + maxItems: 2 not new for your patch, but nit that "Mhz" should be "MHz". Also, maybe the above can be expressed by: assigned-clock-rates: items: - const: 192000000 $ref: "/schemas/types.yaml#/definitions/uint32" - oneOf: # If SS mode - minimum: 125000000 $ref: "/schemas/types.yaml#/definitions/uint32" # If HS mode - minimum: 60000000 $ref: "/schemas/types.yaml#/definitions/uint32" ...it's a little silly to specify that a number has to be either >= 60 MHz or >= 125 MHz but I'm not sure how to express it otherwise... > + resets: > + maxItems: 1 > + description: Phandle to reset control that resets core and wrapper. > + > + interrupts: > + description: > + specifies interrupts from controller wrapper used > + to wakeup from low power/suspend state.Must contain > + one or more entry for interrupt-names property Make the description proper sentences: start with a capital letter, include a space after your period, and end with a period. > + interrupt-names: > + $ref: /schemas/types.yaml#/definitions/string-array > + items: > + #The interrupt that is asserted when a wakeup event > + #is received on USB2 bus Like "clocks", I think these comments can be moved as "description" in the "interrupts" section. > + - const: hs_phy_irq > + #The interrupt that is asserted when a wakeup event > + #is received on USB3 bus > + - const: ss_phy_irq > + #Separate interrupts for any wakeup event on DM and DP lines > + - const: dm_hs_phy_irq > + - const: dp_hs_phy_irq > + > + qcom,select-utmi-as-pipe-clk: > + description: > + if present, disable USB3 pipe_clk requirement. > + Used when dwc3 operates without SSPHY and only > + HS/FS/LS modes are supported. Start description with a capital letter? > + type: boolean > + > +#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. Probably we should pick a name and list it as a real thing, not just a comment. I think you have "type: object". So maybe: patternProperties: "^dwc3@[0-9a-f]+$": type: object description: A child node must exist to represent the core DWC3 IP block The content of the node is defined in dwc3.txt. Eventually maybe we can include the "dwc3.yaml" file once it's created? > +#Phy documentation is provided in the following places: > +#Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt - USB3 QMP PHY > +#Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt - USB2 QUSB2 PHY Comments usually have a space after the "#". See example-schema.yaml. I wonder if this even needs to be here, though. > +required: > + - compatible > + - reg > + - power-domains > + - clocks > + - clock-names > + - assigned-clocks > + - assigned-clock-rates If I'm reading the old bindings properly "assigned-clocks" and "assigned-clock-rates" were previously not "required". > + > +examples: > + - | > + hs_phy: phy@100f8800 { > + compatible = "qcom,qusb2-v2-phy"; > + ... > + }; Your indentation for this whole example is off. The braces don't line up properly. > + > + ss_phy: phy@100f8830 { > + compatible = "qcom,qmp-v3-usb3-phy"; > + ... > + }; > + > + usb3_0: usb30@a6f8800 { > + compatible = "qcom,dwc3"; > + reg = <0xa6f8800 0x400>; > + #address-cells = <1>; > + #size-cells = <1>; > + ranges; #address-cells, #size-cells, and ranges are not documented in the schema. Do they need to be? > + > + interrupts = <0 131 0>, <0 486 0>, <0 488 0>, <0 489 0>; > + interrupt-names = "hs_phy_irq", "ss_phy_irq", > + "dm_hs_phy_irq", "dp_hs_phy_irq"; > + > + clocks = <&gcc GCC_USB30_PRIM_MASTER_CLK>, > + <&gcc GCC_USB30_PRIM_MOCK_UTMI_CLK>, > + <&gcc GCC_USB30_PRIM_SLEEP_CLK>; > + clock-names = "core", "mock_utmi", "sleep"; > + > + assigned-clocks = <&gcc GCC_USB30_PRIM_MOCK_UTMI_CLK>, > + <&gcc GCC_USB30_PRIM_MASTER_CLK>; > + assigned-clock-rates = <19200000>, <133000000>; > + > + resets = <&gcc GCC_USB30_PRIM_BCR>; > + reset-names = "core_reset"; The 'reset-names' property is not in the schema and it doesn't appear to be removed. Remove from the example. > + power-domains = <&gcc USB30_PRIM_GDSC>; > + qcom,select-utmi-as-pipe-clk; > + > + dwc3@10000000 { > + compatible = "snps,dwc3"; > + reg = <0x10000000 0xcd00>; > + interrupts = <0 205 0x4>; > + phys = <&hs_phy>, <&ss_phy>; > + phy-names = "usb2-phy", "usb3-phy"; > + dr_mode = "host"; > + }; > + }; -Doug On Thu, Nov 28, 2019 at 3:33 AM Sandeep Maheswaram wrote: > > Convert USB DWC3 bindings to DT schema format using json-schema. > > Signed-off-by: Sandeep Maheswaram > --- > .../devicetree/bindings/usb/qcom,dwc3.txt | 104 -------------- > .../devicetree/bindings/usb/qcom,dwc3.yaml | 155 +++++++++++++++++++++ > 2 files changed, 155 insertions(+), 104 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/usb/qcom,dwc3.txt > create mode 100644 Documentation/devicetree/bindings/usb/qcom,dwc3.yaml > > diff --git a/Documentation/devicetree/bindings/usb/qcom,dwc3.txt b/Documentation/devicetree/bindings/usb/qcom,dwc3.txt > deleted file mode 100644 > index cb695aa..0000000 > --- a/Documentation/devicetree/bindings/usb/qcom,dwc3.txt > +++ /dev/null > @@ -1,104 +0,0 @@ > -Qualcomm SuperSpeed DWC3 USB SoC controller > - > -Required properties: > -- compatible: Compatible list, contains > - "qcom,dwc3" > - "qcom,msm8996-dwc3" for msm8996 SOC. > - "qcom,msm8998-dwc3" for msm8998 SOC. > - "qcom,sdm845-dwc3" for sdm845 SOC. > -- reg: Offset and length of register set for QSCRATCH wrapper > -- power-domains: specifies a phandle to PM domain provider node > -- 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 > - "mock_utmi" Mock utmi clock needed for ITP/SOF generation in > - host mode. Its frequency should be 19.2MHz. > - "sleep" Sleep clock, used for wakeup when USB3 core goes > - into low power mode (U3). > - > -Optional clocks: > - "iface" System bus AXI clock. > - Not present on "qcom,msm8996-dwc3" compatible. > - "cfg_noc" System Config NOC clock. > - Not present on "qcom,msm8996-dwc3" compatible. > -- assigned-clocks: Should be: > - MOCK_UTMI_CLK > - MASTER_CLK > -- assigned-clock-rates: Should be: > - 19.2Mhz (192000000) for MOCK_UTMI_CLK > - >=125Mhz (125000000) for MASTER_CLK in SS mode > - >=60Mhz (60000000) for MASTER_CLK in HS mode > - > -Optional properties: > -- resets: Phandle to reset control that resets core and wrapper. > -- interrupts: specifies interrupts from controller wrapper used > - to wakeup from low power/susepnd state. Must contain > - one or more entry for interrupt-names property > -- interrupt-names: Must include the following entries: > - - "hs_phy_irq": The interrupt that is asserted when a > - wakeup event is received on USB2 bus > - - "ss_phy_irq": The interrupt that is asserted when a > - wakeup event is received on USB3 bus > - - "dm_hs_phy_irq" and "dp_hs_phy_irq": Separate > - interrupts for any wakeup event on DM and DP lines > -- qcom,select-utmi-as-pipe-clk: if present, disable USB3 pipe_clk requirement. > - Used when dwc3 operates without SSPHY and only > - HS/FS/LS modes are supported. > - > -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. > - > -Phy documentation is provided in the following places: > -Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt - USB3 QMP PHY > -Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt - USB2 QUSB2 PHY > - > -Example device nodes: > - > - hs_phy: phy@100f8800 { > - compatible = "qcom,qusb2-v2-phy"; > - ... > - }; > - > - ss_phy: phy@100f8830 { > - compatible = "qcom,qmp-v3-usb3-phy"; > - ... > - }; > - > - usb3_0: usb30@a6f8800 { > - compatible = "qcom,dwc3"; > - reg = <0xa6f8800 0x400>; > - #address-cells = <1>; > - #size-cells = <1>; > - ranges; > - > - interrupts = <0 131 0>, <0 486 0>, <0 488 0>, <0 489 0>; > - interrupt-names = "hs_phy_irq", "ss_phy_irq", > - "dm_hs_phy_irq", "dp_hs_phy_irq"; > - > - clocks = <&gcc GCC_USB30_PRIM_MASTER_CLK>, > - <&gcc GCC_USB30_PRIM_MOCK_UTMI_CLK>, > - <&gcc GCC_USB30_PRIM_SLEEP_CLK>; > - clock-names = "core", "mock_utmi", "sleep"; > - > - assigned-clocks = <&gcc GCC_USB30_PRIM_MOCK_UTMI_CLK>, > - <&gcc GCC_USB30_PRIM_MASTER_CLK>; > - assigned-clock-rates = <19200000>, <133000000>; > - > - resets = <&gcc GCC_USB30_PRIM_BCR>; > - reset-names = "core_reset"; > - power-domains = <&gcc USB30_PRIM_GDSC>; > - qcom,select-utmi-as-pipe-clk; > - > - dwc3@10000000 { > - compatible = "snps,dwc3"; > - reg = <0x10000000 0xcd00>; > - interrupts = <0 205 0x4>; > - phys = <&hs_phy>, <&ss_phy>; > - phy-names = "usb2-phy", "usb3-phy"; > - dr_mode = "host"; > - }; > - }; > - > diff --git a/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml > new file mode 100644 > index 0000000..48ff9c5 > --- /dev/null > +++ b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml > @@ -0,0 +1,155 @@ > +# SPDX-License-Identifier: GPL-2.0-only > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/usb/qcom,dwc3.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Qualcomm SuperSpeed DWC3 USB SoC controller > + > +maintainers: > + - Manu Gautam > + > +properties: > + compatible: > + items: > + - enum: > + - qcom,msm8996-dwc3 > + - qcom,msm8998-dwc3 > + - qcom,sdm845-dwc3 > + - const: qcom,dwc3 > + > + reg: > + description: Offset and length of register set for QSCRATCH wrapper > + maxItems: 1 > + > + power-domains: > + description: specifies a phandle to PM domain provider node > + maxItems: 1 > + > + clocks: > + description: > + A list of phandle and clock-specifier pairs for the clocks > + listed in clock-names. > + maxItems: 5 > + > + clock-names: > + maxItems: 5 > + items: > + #Master/Core clock, have to be >= 125 MHz for SS operation > + # and >= 60MHz for HS operation > + - const: core > + #Mock utmi clock needed for ITP/SOF generation in host mode. > + #Its frequency should be 19.2MHz. > + - const: mock_utmi > + #Sleep clock, used for wakeup when USB3 core goes into low power mode (U3). > + - const: sleep > + #Optional:System bus AXI clock.Not present on "qcom,msm8996-dwc3" compatible. > + - const: iface > + #Optional:System Config NOC clock.Not present on "qcom,msm8996-dwc3" compatible. > + - const: cfg_noc > + > + assigned-clocks: > + description: > + Should be MOCK_UTMI_CLK and MASTER_CLK > + maxItems: 2 > + > + assigned-clock-rates: > + description: > + Should be 19.2Mhz (192000000) for MOCK_UTMI_CLK > + >=125Mhz (125000000) for MASTER_CLK in SS mode > + >=60Mhz (60000000) for MASTER_CLK in HS mode > + maxItems: 2 > + > + resets: > + maxItems: 1 > + description: Phandle to reset control that resets core and wrapper. > + > + interrupts: > + description: > + specifies interrupts from controller wrapper used > + to wakeup from low power/suspend state.Must contain > + one or more entry for interrupt-names property > + > + interrupt-names: > + $ref: /schemas/types.yaml#/definitions/string-array > + items: > + #The interrupt that is asserted when a wakeup event > + #is received on USB2 bus > + - const: hs_phy_irq > + #The interrupt that is asserted when a wakeup event > + #is received on USB3 bus > + - const: ss_phy_irq > + #Separate interrupts for any wakeup event on DM and DP lines > + - const: dm_hs_phy_irq > + - const: dp_hs_phy_irq > + > + qcom,select-utmi-as-pipe-clk: > + description: > + if present, disable USB3 pipe_clk requirement. > + Used when dwc3 operates without SSPHY and only > + HS/FS/LS modes are supported. > + type: boolean > + > +#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. > + > +#Phy documentation is provided in the following places: > +#Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt - USB3 QMP PHY > +#Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt - USB2 QUSB2 PHY > + > +required: > + - compatible > + - reg > + - power-domains > + - clocks > + - clock-names > + - assigned-clocks > + - assigned-clock-rates > + > +examples: > + - | > + hs_phy: phy@100f8800 { > + compatible = "qcom,qusb2-v2-phy"; > + ... > + }; > + > + ss_phy: phy@100f8830 { > + compatible = "qcom,qmp-v3-usb3-phy"; > + ... > + }; > + > + usb3_0: usb30@a6f8800 { > + compatible = "qcom,dwc3"; > + reg = <0xa6f8800 0x400>; > + #address-cells = <1>; > + #size-cells = <1>; > + ranges; > + > + interrupts = <0 131 0>, <0 486 0>, <0 488 0>, <0 489 0>; > + interrupt-names = "hs_phy_irq", "ss_phy_irq", > + "dm_hs_phy_irq", "dp_hs_phy_irq"; > + > + clocks = <&gcc GCC_USB30_PRIM_MASTER_CLK>, > + <&gcc GCC_USB30_PRIM_MOCK_UTMI_CLK>, > + <&gcc GCC_USB30_PRIM_SLEEP_CLK>; > + clock-names = "core", "mock_utmi", "sleep"; > + > + assigned-clocks = <&gcc GCC_USB30_PRIM_MOCK_UTMI_CLK>, > + <&gcc GCC_USB30_PRIM_MASTER_CLK>; > + assigned-clock-rates = <19200000>, <133000000>; > + > + resets = <&gcc GCC_USB30_PRIM_BCR>; > + reset-names = "core_reset"; > + power-domains = <&gcc USB30_PRIM_GDSC>; > + qcom,select-utmi-as-pipe-clk; > + > + dwc3@10000000 { > + compatible = "snps,dwc3"; > + reg = <0x10000000 0xcd00>; > + interrupts = <0 205 0x4>; > + phys = <&hs_phy>, <&ss_phy>; > + phy-names = "usb2-phy", "usb3-phy"; > + dr_mode = "host"; > + }; > + }; > -- > QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member > of Code Aurora Forum, hosted by The Linux Foundation >