devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wesley Cheng <wesley.cheng@oss.qualcomm.com>,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	konrad.dybcio@oss.qualcomm.com,
	dmitry.baryshkov@oss.qualcomm.com, kishon@kernel.org,
	vkoul@kernel.org, gregkh@linuxfoundation.org, robh@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 02/10] dt-bindings: phy: qcom,qmp-usb: Add Glymur USB UNI PHY compatible
Date: Sat, 11 Oct 2025 02:04:15 +0200	[thread overview]
Message-ID: <f5e4ae02-b8fa-4406-b2e0-3602b07b7e23@kernel.org> (raw)
In-Reply-To: <20251006222002.2182777-3-wesley.cheng@oss.qualcomm.com>

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@oss.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

  reply	other threads:[~2025-10-11  0:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06 22:19 [PATCH v5 00/10] Introduce Glymur USB support Wesley Cheng
2025-10-06 22:19 ` [PATCH v5 01/10] dt-bindings: phy: qcom,sc8280xp-qmp-usb43dp-phy: Add Glymur compatible Wesley Cheng
2025-10-08  0:42   ` Rob Herring
2025-10-06 22:19 ` [PATCH v5 02/10] dt-bindings: phy: qcom,qmp-usb: Add Glymur USB UNI PHY compatible Wesley Cheng
2025-10-11  0:04   ` Krzysztof Kozlowski [this message]
2025-10-13 23:44     ` Wesley Cheng
2025-10-13 23:46       ` Wesley Cheng
2025-10-13 23:50         ` Krzysztof Kozlowski
2025-10-14  1:16           ` Wesley Cheng
2025-10-14  4:36             ` Krzysztof Kozlowski
2025-10-17  0:15               ` Wesley Cheng
2025-10-17  4:41                 ` Krzysztof Kozlowski
2025-10-18  0:20                   ` Wesley Cheng
2025-10-18 15:39                     ` Krzysztof Kozlowski
2025-10-21 22:51                       ` Wesley Cheng
2025-10-06 22:19 ` [PATCH v5 03/10] dt-bindings: phy: qcom-m31-eusb2: Add Glymur compatible Wesley Cheng
2025-10-11  0:01   ` Krzysztof Kozlowski
2025-10-06 22:19 ` [PATCH v5 04/10] dt-bindings: usb: qcom,snps-dwc3: " Wesley Cheng
2025-10-07  7:47   ` Krzysztof Kozlowski
2025-10-06 22:19 ` [PATCH v5 05/10] dt-bindings: phy: qcom,snps-eusb2-repeater: Add SMB2370 compatible Wesley Cheng
2025-10-07  7:45   ` Krzysztof Kozlowski
2025-10-06 22:19 ` [PATCH v5 06/10] phy: qualcomm: Update the QMP clamp register for V6 Wesley Cheng
2025-10-06 22:19 ` [PATCH v5 07/10] phy: qualcomm: qmp-combo: Update QMP PHY with Glymur settings Wesley Cheng
2025-10-24 10:04   ` Abel Vesa
2025-10-25  0:02     ` Wesley Cheng
2025-10-25  0:41       ` Wesley Cheng
2025-10-28 21:10         ` Dmitry Baryshkov
2025-10-06 22:20 ` [PATCH v5 08/10] phy: qualcomm: qmp-usb: Add support for Glymur USB UNI PHY Wesley Cheng
2025-10-06 22:20 ` [PATCH v5 09/10] phy: qualcomm: m31-eusb2: Make clkref an optional resource Wesley Cheng
2025-10-06 22:20 ` [PATCH v5 10/10] phy: qualcomm: eusb2-repeater: Add SMB2370 eUSB2 repeater support Wesley Cheng
2025-10-07  1:02 ` [PATCH v5 00/10] Introduce Glymur USB support Krzysztof Kozlowski
2025-10-07  1:05   ` Wesley Cheng
2025-10-07  1:47     ` Krzysztof Kozlowski
2025-10-08  3:31   ` Dmitry Baryshkov

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=f5e4ae02-b8fa-4406-b2e0-3602b07b7e23@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kishon@kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=vkoul@kernel.org \
    --cc=wesley.cheng@oss.qualcomm.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 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).