LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Doug Anderson <dianders@chromium.org>
To: Sandeep Maheswaram <sanm@codeaurora.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Felipe Balbi <balbi@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
linux-usb@vger.kernel.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Manu Gautam <mgautam@codeaurora.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: usb: qcom,dwc3: Convert USB DWC3 bindings
Date: Tue, 17 Dec 2019 11:14:17 -0800 [thread overview]
Message-ID: <CAD=FV=U48gdGHMbQ22M_59t6va2n41Zh1CDTqMJYpLCwiD35Mg@mail.gmail.com> (raw)
In-Reply-To: <1576474742-23409-2-git-send-email-sanm@codeaurora.org>
Hi,
On Sun, Dec 15, 2019 at 9:40 PM Sandeep Maheswaram <sanm@codeaurora.org> 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..c8eda58
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> @@ -0,0 +1,153 @@
> +# 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 <mgautam@codeaurora.org>
> +
> +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
> +
> + "#address-cells":
> + enum: [ 1, 2 ]
> +
> + "#size-cells":
> + enum: [ 1, 2 ]
> +
> + 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.
> + minItems: 3
Actually, maybe the best way to express the min/max is to match what
'gpu/arm,mali-midgard.yaml' does. Specifically later down in the
bindings you can amend this, like this I think:
allOf:
- if:
properties:
compatible:
contains:
const: "qcom,msm8996-dwc3"
then:
properties:
clocks:
minItems: 3
maxItems: 3
clock-names:
minItems: 3
maxItems: 3
...then remove minItems from here. Now you'll have the default
min/max of 5 for most devices but for the special case of
"qcom,msm8996-dwc3" you'll have min/max of 3.
> + items:
> + - description: System Config NOC clock. Not present on "qcom,msm8996-dwc3" compatible.
> + - description: Master/Core clock, have to be >= 125 MHz for SS operation and >= 60MHz for HS operation
To make the grammer gooder, s/have/has/
> + - description: System bus AXI clock. Not present on "qcom,msm8996-dwc3" compatible.
> + - description: Mock utmi clock needed for ITP/SOF generation in host mode.Its frequency should be 19.2MHz.
> + - description: Sleep clock, used for wakeup when USB3 core goes into low power mode (U3).
* Please word wrap to ~80 chracters.
* As Stephen says, order matters. Please match order of old bindings
(and in clock-names)
* Please end each with a period.
> + clock-names:
> + minItems: 3
> + items:
> + - const: cfg_noc
> + - const: core
> + - const: iface
> + - const: mock_utmi
> + - const: sleep
> +
> + assigned-clocks:
> + items:
> + - description: Phandle to MOCK_UTMI_CLK.
> + - description: Phandle to MASTER_CLK.
> +
> + assigned-clock-rates:
> + description:
> + Should be 19.2MHz (19200000) for MOCK_UTMI_CLK
> + >=125MHz (125000000) for MASTER_CLK in SS mode
> + >=60MHz (60000000) for MASTER_CLK in HS mode
> + maxItems: 2
You can still express some limits here even if we don't go all out
with the "oneOf". AKA I think this is better:
assigned-clock-rates:
items:
- const: 19200000
- minimum: 60000000
description: >= 60 MHz in HS mode, >= 125 MHz in SS mode
> + resets:
> + maxItems: 1
> +
> + 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.
Now that sub-items have a description this top level description
doesn't add anything. Delete.
> + items:
> + - description: The interrupt that is asserted when a wakeup event is received on USB2 bus.
> + - description: The interrupt that is asserted when a wakeup event is received on USB3 bus.
Word wrap please.
> + - description: Wakeup event on DM line.
> + - description: Wakeup event on DP line.
> +
> + interrupt-names:
> + $ref: /schemas/types.yaml#/definitions/string-array
As Rob said in response to your previous version: "Already has a type,
don't need."
> + items:
> + - const: hs_phy_irq
> + - const: ss_phy_irq
> + - 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:
> +
> +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.
> +
> +# 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
> + - "#address-cells"
> + - "#size-cells"
> + - power-domains
> + - clocks
> + - clock-names
> +
> +examples:
> + - |
> + usb3_0: usb30@a6f8800 {
> + compatible = "qcom,dwc3";
Your example is missing the SoC-specific compatible string, so it
fails your own schema.
> + reg = <0xa6f8800 0x400>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges;
> + interrupts = <0 131 0>, <0 486 0>, <0 488 0>, <0 489 0>;
In general I believe "0" is frowned upon for IRQ flags. Your example
should probably be this from sdm845:
interrupts = <GIC_SPI 131 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 486 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 488 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 489 IRQ_TYPE_LEVEL_HIGH>;
...and you'll likely need a #include in the example. See below.
> + interrupt-names = "hs_phy_irq", "ss_phy_irq",
> + "dm_hs_phy_irq", "dp_hs_phy_irq";
> +
> + clocks = <&gcc GCC_USB30_PRIM_MASTER_CLK>,
As Rob requested in the previous version, please run:
make dt_binding_check
DT_SCHEMA_FILES=Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
If the next version doesn't pass "dt_binding_check" I suspect that
people will stop reviewing your change, so please make sure you've
figured out how to do this.
When you do that, you'll see a syntax error here because
"GCC_USB30_PRIM_MASTER_CLK" isn't defined anywhere in your example.
You need to include it. AKA this should be at the top of your
example:
#include <dt-bindings/clock/qcom,gcc-sdm845.h>
next prev parent reply other threads:[~2019-12-17 19:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 5:39 [PATCH v3 0/2] Add USB DWC3 support for SC7180 Sandeep Maheswaram
2019-12-16 5:39 ` [PATCH v3 1/2] dt-bindings: usb: qcom,dwc3: Convert USB DWC3 bindings Sandeep Maheswaram
2019-12-16 18:09 ` Stephen Boyd
2019-12-17 19:22 ` Doug Anderson
[not found] ` <e901331b-456c-f3ed-6717-e5bf24778c57@codeaurora.org>
2019-12-18 18:39 ` Doug Anderson
2019-12-17 19:14 ` Doug Anderson [this message]
[not found] ` <6d8c979f-daa3-3b40-f29c-cca5a2f8f1c8@codeaurora.org>
2019-12-18 18:37 ` Doug Anderson
2019-12-18 22:13 ` Rob Herring
2019-12-26 5:56 ` Sandeep Maheswaram (Temp)
2020-01-07 3:47 ` Doug Anderson
2019-12-16 5:39 ` [PATCH v3 2/2] dt-bindings: usb: qcom,dwc3: Add compatible for SC7180 Sandeep Maheswaram
2019-12-16 18:09 ` Stephen Boyd
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='CAD=FV=U48gdGHMbQ22M_59t6va2n41Zh1CDTqMJYpLCwiD35Mg@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=agross@kernel.org \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mgautam@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sanm@codeaurora.org \
--cc=swboyd@chromium.org \
--subject='Re: [PATCH v3 1/2] dt-bindings: usb: qcom,dwc3: Convert USB DWC3 bindings' \
/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
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).