Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>
Cc: olteanv@gmail.com, neil.armstrong@linaro.org, robh@kernel.org,
	vkoul@kernel.org, linux-phy@lists.infradead.org,
	linux-pci@vger.kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 2/6] dt-bindings: PCI: qcom-ep: Add QCS8300 compatible
Date: Mon, 21 Sep 2026 11:10:05 +0000	[thread overview]
Message-ID: <20260921111005.BE4841F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260921-monaco_ep-v1-2-63c5282fb0db@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dt-bindings: missing QCS8300 compatible string in conditional block
--

commit e543ce399a6b1c737f9d5a524c907cd7d96b4ffb
Author: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>

dt-bindings: PCI: qcom-ep: Add QCS8300 compatible

The QCS8300 PCIe Endpoint controller is compatible with the SA8775P PCIe
Endpoint controller. This commit documents the QCS8300 compatible string
and its fallback to the SA8775P compatible.

> diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie-ep.yaml b/Documentation/devicetree/bindings/pci/qcom,pcie-ep.yaml
> index bed9a40b186bc..7f9a0bc958d1b 100644
> --- a/Documentation/devicetree/bindings/pci/qcom,pcie-ep.yaml
> +++ b/Documentation/devicetree/bindings/pci/qcom,pcie-ep.yaml
> @@ -13,10 +13,15 @@ properties:
>    compatible:
>      oneOf:
>        - enum:
> +          - qcom,qcs8300-pcie-ep
>            - qcom,sa8775p-pcie-ep

[Severity: Medium]
Will a device tree node using only "qcom,qcs8300-pcie-ep" silently bypass
the clock and clock-names constraints?

Since this compatible string is now allowed as standalone in the
properties:compatible:oneOf:enum block, it appears to be missing from the
allOf:if:properties:compatible:contains:enum conditional block enforcing
SA8775P constraints later in the file:

  - if:
      properties:
        compatible:
          contains:
            enum:
              - qcom,sa8775p-pcie-ep
    then:
      properties:
        clocks:
...

Should qcom,qcs8300-pcie-ep be added to this enum as well?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260921-monaco_ep-v1-0-63c5282fb0db@oss.qualcomm.com?part=2

  reply	other threads:[~2026-09-21 11:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 10:58 [PATCH 0/6] PCI: qcom-ep: Add PCIe Endpoint support for Monaco Krishna Chaitanya Chundru
2026-09-21 10:58 ` [PATCH 1/6] dt-bindings: phy: qcom,sc8280xp-qmp-pcie-phy: Add qcs8300 16 GT/s PHY Krishna Chaitanya Chundru
2026-09-21 11:05   ` sashiko-bot
2026-09-25 13:10   ` Krzysztof Kozlowski
2026-09-21 10:58 ` [PATCH 2/6] dt-bindings: PCI: qcom-ep: Add QCS8300 compatible Krishna Chaitanya Chundru
2026-09-21 11:10   ` sashiko-bot [this message]
2026-09-25 13:16   ` Krzysztof Kozlowski
2026-09-21 10:58 ` [PATCH 3/6] phy: qcom: qmp-pcie: Add endpoint PHY configuration for QCS8300 Krishna Chaitanya Chundru
2026-09-21 11:19   ` sashiko-bot
2026-09-23 12:19   ` Konrad Dybcio
2026-09-23 12:30     ` Krishna Chaitanya Chundru
2026-09-25 15:32   ` Manivannan Sadhasivam
2026-09-21 10:58 ` [PATCH 4/6] PCI: qcom-ep: Set initial interconnect bandwidth before enabling clocks Krishna Chaitanya Chundru
2026-09-21 11:25   ` sashiko-bot
2026-09-21 10:58 ` [PATCH 5/6] arm64: qcom: monaco: Fix pcie1_phy compatible to list qcs8300 first Krishna Chaitanya Chundru
2026-09-21 11:30   ` sashiko-bot
2026-09-23 12:32   ` Konrad Dybcio
2026-09-21 10:58 ` [PATCH 6/6] arm64: qcom: monaco: Add PCIe Endpoint nodes Krishna Chaitanya Chundru
2026-09-21 11:40   ` sashiko-bot

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=20260921111005.BE4841F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krishna.chundru@oss.qualcomm.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --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