From: Rob Herring <robh@kernel.org>
To: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Felipe Balbi <balbi@kernel.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
Saravana Kannan <saravanak@google.com>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Frank Li <Frank.li@nxp.com>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/7] dt-bindings: usb: Introduce qcom,snps-dwc3
Date: Fri, 28 Feb 2025 16:36:14 -0600 [thread overview]
Message-ID: <20250228223614.GA3792644-robh@kernel.org> (raw)
In-Reply-To: <20250226-dwc3-refactor-v4-1-4415e7111e49@oss.qualcomm.com>
On Wed, Feb 26, 2025 at 04:17:48PM -0800, Bjorn Andersson wrote:
> The Qualcomm USB glue is not separate of the Synopsys DWC3 core and
> several of the snps,dwc3 properties (such as clocks and reset) conflicts
> in expectation with the Qualcomm integration.
>
> Using the newly split out Synopsys DWC3 core properties, describe the
> Qualcomm USB block in a single block. The new binding is a copy of
> qcom,dwc3 with the needed modifications.
>
> It would have been convenient to retain the two structures with the same
> compatibles, but as there exist no way to select a binding based on the
> absence of a subnode/patternProperty, a new generic compatible is
> introduced to describe this binding.
>
> To avoid redefining all the platform-specific compatibles, "select" is
> used to tell the DeviceTree validator which binding to use solely on the
> generic compatible. (Otherwise if the specific compatible matches during
> validation, the generic one must match as well)
>
> Mark qcom,dwc3 deprecated, to favor expressing future platforms using
> the new combined binding.
>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> ---
> .../devicetree/bindings/usb/qcom,dwc3.yaml | 13 +-
> .../devicetree/bindings/usb/qcom,snps-dwc3.yaml | 619 +++++++++++++++++++++
> 2 files changed, 631 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> index a2b3cf625e5b..6d818e6dddbc 100644
> --- a/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> +++ b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> @@ -4,11 +4,22 @@
> $id: http://devicetree.org/schemas/usb/qcom,dwc3.yaml#
> $schema: http://devicetree.org/meta-schemas/core.yaml#
>
> -title: Qualcomm SuperSpeed DWC3 USB SoC controller
> +title: Legacy Qualcomm SuperSpeed DWC3 USB SoC controller
>
> maintainers:
> - Wesley Cheng <quic_wcheng@quicinc.com>
>
> +# Use the combined qcom,snps-dwc3 instead
> +deprecated: true
> +
> +select:
> + properties:
> + compatible:
> + contains:
> + const: qcom,dwc3
> + required:
> + - compatible
> +
> properties:
> compatible:
> items:
> diff --git a/Documentation/devicetree/bindings/usb/qcom,snps-dwc3.yaml b/Documentation/devicetree/bindings/usb/qcom,snps-dwc3.yaml
> new file mode 100644
> index 000000000000..37af52e01803
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/qcom,snps-dwc3.yaml
> @@ -0,0 +1,619 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/usb/qcom,snps-dwc3.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm SuperSpeed DWC3 USB SoC controller
> +
> +maintainers:
> + - Wesley Cheng <quic_wcheng@quicinc.com>
> +
> +description:
> + Describes the Qualcomm USB block, based on Synopsys DWC3.
> +
> +select:
> + properties:
> + compatible:
> + contains:
> + const: qcom,snps-dwc3
> + required:
> + - compatible
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - qcom,ipq4019-dwc3
> + - qcom,ipq5018-dwc3
> + - qcom,ipq5332-dwc3
> + - qcom,ipq5424-dwc3
> + - qcom,ipq6018-dwc3
> + - qcom,ipq8064-dwc3
> + - qcom,ipq8074-dwc3
> + - qcom,ipq9574-dwc3
> + - qcom,msm8953-dwc3
> + - qcom,msm8994-dwc3
> + - qcom,msm8996-dwc3
> + - qcom,msm8998-dwc3
> + - qcom,qcm2290-dwc3
> + - qcom,qcs404-dwc3
> + - qcom,qcs615-dwc3
> + - qcom,qcs8300-dwc3
> + - qcom,qdu1000-dwc3
> + - qcom,sa8775p-dwc3
> + - qcom,sar2130p-dwc3
> + - qcom,sc7180-dwc3
> + - qcom,sc7280-dwc3
> + - qcom,sc8180x-dwc3
> + - qcom,sc8180x-dwc3-mp
> + - qcom,sc8280xp-dwc3
> + - qcom,sc8280xp-dwc3-mp
> + - qcom,sdm660-dwc3
> + - qcom,sdm670-dwc3
> + - qcom,sdm845-dwc3
> + - qcom,sdx55-dwc3
> + - qcom,sdx65-dwc3
> + - qcom,sdx75-dwc3
> + - qcom,sm4250-dwc3
> + - qcom,sm6115-dwc3
> + - qcom,sm6125-dwc3
> + - qcom,sm6350-dwc3
> + - qcom,sm6375-dwc3
> + - qcom,sm8150-dwc3
> + - qcom,sm8250-dwc3
> + - qcom,sm8350-dwc3
> + - qcom,sm8450-dwc3
> + - qcom,sm8550-dwc3
> + - qcom,sm8650-dwc3
> + - qcom,x1e80100-dwc3
> + - const: qcom,snps-dwc3
> +
> + reg:
> + description: Offset and length of register set for QSCRATCH wrapper
I think you want to drop this. Or do you need 2 regions? The wrapper
regs and the DWC3 regs? Probably worth describing separately even if
they are adjacent currently.
> + maxItems: 1
> +
> + power-domains:
> + description: specifies a phandle to PM domain provider node
Drop the description.
Otherwise, looks good.
Rob
next prev parent reply other threads:[~2025-02-28 22:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 0:17 [PATCH v4 0/7] usb: dwc3: qcom: Flatten dwc3 structure Bjorn Andersson
2025-02-27 0:17 ` [PATCH v4 1/7] dt-bindings: usb: Introduce qcom,snps-dwc3 Bjorn Andersson
2025-02-28 22:36 ` Rob Herring [this message]
2025-03-03 22:11 ` Bjorn Andersson
2025-02-27 0:17 ` [PATCH v4 2/7] usb: dwc3: core: Expose core driver as library Bjorn Andersson
2025-02-27 19:17 ` Frank Li
2025-02-27 0:17 ` [PATCH v4 3/7] usb: dwc3: core: Don't touch resets and clocks Bjorn Andersson
2025-02-27 4:24 ` Dmitry Baryshkov
2025-02-27 15:55 ` Bjorn Andersson
2025-02-27 16:07 ` Dmitry Baryshkov
2025-02-27 19:22 ` Frank Li
2025-02-27 0:17 ` [PATCH v4 4/7] usb: dwc3: qcom: Don't rely on drvdata during probe Bjorn Andersson
2025-02-27 0:17 ` [PATCH v4 5/7] usb: dwc3: qcom: Snapshot driver for backwards compatibilty Bjorn Andersson
2025-03-04 0:05 ` Thinh Nguyen
2025-03-04 0:39 ` Thinh Nguyen
2025-03-04 3:13 ` Bjorn Andersson
2025-03-05 0:31 ` Thinh Nguyen
2025-03-06 22:49 ` Bjorn Andersson
2025-03-07 16:17 ` Frank Li
2025-03-07 23:00 ` Thinh Nguyen
2025-03-07 23:16 ` Thinh Nguyen
2025-03-11 3:06 ` Bjorn Andersson
2025-03-11 23:59 ` Thinh Nguyen
2025-02-27 0:17 ` [PATCH v4 6/7] usb: dwc3: qcom: Transition to flattened model Bjorn Andersson
2025-03-07 6:41 ` Dmitry Baryshkov
2025-03-11 2:46 ` Bjorn Andersson
2025-03-11 19:02 ` Dmitry Baryshkov
2025-03-18 19:12 ` Bjorn Andersson
2025-02-27 0:17 ` [PATCH v4 7/7] arm64: dts: qcom: sc8280x: Flatten the USB nodes Bjorn Andersson
2025-03-08 17:58 ` Konrad Dybcio
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=20250228223614.GA3792644-robh@kernel.org \
--to=robh@kernel.org \
--cc=Frank.li@nxp.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=andersson@kernel.org \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=quic_wcheng@quicinc.com \
--cc=saravanak@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.