[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f5e4ae02-b8fa-4406-b2e0-3602b07b7e23@kernel.org>
Date: Sat, 11 Oct 2025 02:04:15 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Wesley Cheng <wesley.cheng@....qualcomm.com>, krzk+dt@...nel.org,
conor+dt@...nel.org, konrad.dybcio@....qualcomm.com,
dmitry.baryshkov@....qualcomm.com, kishon@...nel.org, vkoul@...nel.org,
gregkh@...uxfoundation.org, robh@...nel.org
Cc: linux-arm-msm@...r.kernel.org, linux-phy@...ts.infradead.org,
linux-usb@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 02/10] dt-bindings: phy: qcom,qmp-usb: Add Glymur USB
UNI PHY compatible
On 07/10/2025 00:19, Wesley Cheng wrote:
> The Glymur USB subsystem contains a multiport controller, which utilizes
> two QMP UNI PHYs. Add the proper compatible string for the Glymur SoC, and
> the required clkref clock name.
>
> Signed-off-by: Wesley Cheng <wesley.cheng@....qualcomm.com>
> ---
> .../phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml | 35 +++++++++++++++++++
> 1 file changed, 35 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml
> index a1b55168e050..b0ce803d2b49 100644
> --- a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml
> @@ -16,6 +16,7 @@ description:
> properties:
> compatible:
> enum:
> + - qcom,glymur-qmp-usb3-uni-phy
> - qcom,ipq5424-qmp-usb3-phy
> - qcom,ipq6018-qmp-usb3-phy
> - qcom,ipq8074-qmp-usb3-phy
> @@ -62,6 +63,8 @@ properties:
>
> vdda-pll-supply: true
>
> + refgen-supply: true
> +
> "#clock-cells":
> const: 0
>
> @@ -157,6 +160,25 @@ allOf:
> compatible:
> contains:
> enum:
> + - qcom,glymur-qmp-usb3-uni-phy
> + then:
> + properties:
> + clocks:
Missing minItems.
> + maxItems: 5
> + clock-names:
> + items:
> + - const: aux
> + - const: clkref
> + - const: ref
What is the difference between these two? Which block INPUTs
(important!) they represent?
> + - const: com_aux
> + - const: pipe
> +
> + - if:
Best regards,
Krzysztof
Powered by blists - more mailing lists