Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Nitin Rawat" <nitin.rawat@oss.qualcomm.com>
Cc: olteanv@gmail.com, conor+dt@kernel.org, vkoul@kernel.org,
	robh@kernel.org, devicetree@vger.kernel.org,
	neil.armstrong@linaro.org, linux-phy@lists.infradead.org
Subject: Re: [PATCH V1] dt-bindings: phy: qcom,sc8280xp-qmp-ufs-phy: Add QMP UFS PHY compatible for Maili
Date: Fri, 14 Aug 2026 01:56:15 +0000	[thread overview]
Message-ID: <20260814015615.6C9D51F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260814004725.1368027-1-nitin.rawat@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The new compatible strings `qcom,maili-qmp-ufs-phy` and `qcom,hawi-qmp-ufs-phy` are omitted from the `allOf` conditional blocks that enforce strict constraints for clocks.
- [Medium] The fallback compatible `qcom,hawi-qmp-ufs-phy` is not defined as a standalone base compatible in the schema.
--

--- Patch [1]: [PATCH V1] dt-bindings: phy: qcom,sc8280xp-qmp-ufs-phy: Add QMP UFS PHY compatible for Maili ---
commit c983ddf99ae7f556a6b7a2870c88327054b94d8c
Author: Nitin Rawat <nitin.rawat@oss.qualcomm.com>

dt-bindings: phy: qcom,sc8280xp-qmp-ufs-phy: Add QMP UFS PHY compatible for Maili

Document the QMP UFS PHY compatible for Qualcomm Maili to support
physical layer functionality for UFS found on the SoC. Use fallback to
indicate the compatibility of the QMP UFS PHY on the Maili with that on
the Hawi.

> diff --git a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-ufs-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-ufs-phy.yaml
> index b2c5c9a375a35..f74434f51653c 100644
> --- a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-ufs-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-ufs-phy.yaml
> @@ -16,6 +16,10 @@ description:
>  properties:
>    compatible:
>      oneOf:
> +      - items:
> +          - enum:
> +              - qcom,maili-qmp-ufs-phy
> +          - const: qcom,hawi-qmp-ufs-phy

[Severity: Medium]
If qcom,hawi-qmp-ufs-phy is used as a fallback here, shouldn't it also
be added to the standalone enum list further down in this file at line 42
under properties:compatible:oneOf:enum?

Without it being defined as a standalone compatible string, a device tree
node for the base Hawi hardware using just
compatible = "qcom,hawi-qmp-ufs-phy" will fail schema validation when running
dt_binding_check.


[Severity: Medium]
Do these new compatibles need to be added to the allOf conditional block
that enforces strict clock constraints at line 88?

Currently, Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-ufs-phy.yaml
has an allOf:if block starting at line 88 that enforces a strict 3-clock
limit (ref, ref_aux, qref) for most modern PHYs.

Since they are missing from that enum list, device trees using these new
compatible strings will silently bypass the strict clock constraints and
fall back to the loose global defaults. This regression allows incomplete or
invalid clock configurations to pass dt_binding_check validation.

>        - items:
>            - enum:
>                - qcom,qcs8300-qmp-ufs-phy

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260814004725.1368027-1-nitin.rawat@oss.qualcomm.com?part=1

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

  reply	other threads:[~2026-08-14  1:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  0:47 [PATCH V1] dt-bindings: phy: qcom,sc8280xp-qmp-ufs-phy: Add QMP UFS PHY compatible for Maili Nitin Rawat
2026-08-14  1:56 ` sashiko-bot [this message]
2026-08-14  2:31 ` Jingyi Wang
2026-08-14  6:35   ` Nitin Rawat

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=20260814015615.6C9D51F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=nitin.rawat@oss.qualcomm.com \
    --cc=olteanv@gmail.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vkoul@kernel.org \
    /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