From: sashiko-bot@kernel.org
To: "Krishna Kurapati" <krishna.kurapati@oss.qualcomm.com>
Cc: olteanv@gmail.com, neil.armstrong@linaro.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-phy@lists.infradead.org, vkoul@kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 2/4] dt-bindings: phy: qcs615-qmp-usb3dp: Add support for Shikra SoC
Date: Wed, 01 Jul 2026 16:57:50 +0000 [thread overview]
Message-ID: <20260701165750.9AF511F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260701165051.4122259-3-krishna.kurapati@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The YAML schema fails to enforce the mandatory 3 resets for the Shikra SoC, allowing incomplete device tree nodes to pass validation.
--
commit dd87f88551c8d0851ff72a007e5d3d25aa1a3fc0
Author: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
dt-bindings: phy: qcs615-qmp-usb3dp: Add support for Shikra SoC
Declare the USB-C QMP PHY present on the Qualcomm Shikra SoC. Shikra uses
3 resets to be programmed before initialising the phy. Also, add remote
endpoints and orientation switch support for getting Type-C orientation
information.
> diff --git a/Documentation/devicetree/bindings/phy/qcom,qcs615-qmp-usb3dp-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,qcs615-qmp-usb3dp-phy.yaml
> index efb465c71c1b5..ae3f0dda3bca2 100644
> --- a/Documentation/devicetree/bindings/phy/qcom,qcs615-qmp-usb3dp-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/qcom,qcs615-qmp-usb3dp-phy.yaml
[ ... ]
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - qcom,shikra-qmp-usb3-dp-phy
> + then:
> + properties:
> + resets:
> + maxItems: 3
> + reset-names:
> + items:
> + - const: phy_phy
> + - const: dp_phy
> + - const: phy
[Severity: Medium]
Does this schema accurately enforce the 3 mandatory resets for the Shikra SoC?
The base schema sets minItems to 2 for both resets and reset-names. Because
this conditional block only specifies maxItems: 3 and lists the items without
overriding minItems to 3, the schema will evaluate with minItems: 2 for
Shikra.
Could this allow incomplete device tree nodes missing the required third
reset to silently pass validation during a dt_binding_check run?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260701165051.4122259-1-krishna.kurapati@oss.qualcomm.com?part=2
next prev parent reply other threads:[~2026-07-01 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 16:50 [PATCH v4 0/4] Add USB Phy driver and binding changes for Qualcomm Shikra SoC Krishna Kurapati
2026-07-01 16:50 ` [PATCH v4 1/4] dt-bindings: phy: qcom,qusb2: Document QUSB2 Phy for Shikra Krishna Kurapati
2026-07-01 16:50 ` [PATCH v4 2/4] dt-bindings: phy: qcs615-qmp-usb3dp: Add support for Shikra SoC Krishna Kurapati
2026-07-01 16:57 ` sashiko-bot [this message]
2026-07-01 16:50 ` [PATCH v4 3/4] phy: qcom-qusb2: Add support for Shikra Krishna Kurapati
2026-07-01 17:01 ` sashiko-bot
2026-07-02 13:48 ` Dmitry Baryshkov
2026-07-02 15:54 ` Krishna Kurapati
2026-07-01 16:50 ` [PATCH v4 4/4] phy: qcom: qmp-usbc: Add qmp configuration " Krishna Kurapati
2026-07-01 23:24 ` 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=20260701165750.9AF511F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krishna.kurapati@oss.qualcomm.com \
--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