From: sashiko-bot@kernel.org
To: "Bryan O'Donoghue" <bryan.odonoghue@linaro.org>
Cc: neil.armstrong@linaro.org, devicetree@vger.kernel.org,
linux-phy@lists.infradead.org, robh@kernel.org,
conor+dt@kernel.org, vkoul@kernel.org, olteanv@gmail.com,
media-ci@linuxtv.org
Subject: Re: [PATCH v18 1/2] dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema
Date: Thu, 17 Sep 2026 00:05:37 +0000 [thread overview]
Message-ID: <20260917000537.EB7241F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260917-x1e-csi2-phy-v18-1-6515b5255fa9@linaro.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: phy: qcom: Incomplete constraints for DPHY split-mode
--
commit f4a95bb9fcce6ee77a3c3f8e0b0bc0bc538a0aa7
Author: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema
Add a base schema for the MIPI CSI2 PHYs on Qualcomm SoCs. The schema
supports both C-PHY and D-PHY modes, as well as a split-mode allowing two
sensors to be connected to one PHY.
> diff --git a/Documentation/devicetree/bindings/phy/qcom,x1e80100-csi2-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,x1e80100-csi2-phy.yaml
> new file mode 100644
> index 0000000000000..dc64af97da6c6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/qcom,x1e80100-csi2-phy.yaml
[ ... ]
> + allOf:
> + - if:
> + required:
> + - endpoint@1
> + then:
> + properties:
> + endpoint@0:
> + properties:
> + data-lanes:
> + maxItems: 2
> + items:
> + maximum: 2
> + endpoint@1:
> + properties:
> + data-lanes:
> + items:
> + - const: 3
[Severity: Low]
Does this schema lack sufficient constraints for the split-mode endpoints?
The split-mode definition in properties.ports.properties.port@0.allOf appears
to be missing bus-type restrictions, clock-lanes constraints, and an explicit
maxItems restriction for endpoint@1. Without these, a misconfigured device
tree utilizing split-mode with an invalid bus-type, incorrect clock-lanes, or
extra data-lanes on endpoint@1 will pass dt-schema validation silently.
Could explicit constraints be added here to enforce the D-PHY bus-type,
restrict the clock-lanes positions, and strictly limit maxItems?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260917-x1e-csi2-phy-v18-0-6515b5255fa9@linaro.org?part=1
next prev parent reply other threads:[~2026-09-17 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 23:58 [PATCH v18 0/2] phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver Bryan O'Donoghue
2026-09-16 23:58 ` [PATCH v18 1/2] dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema Bryan O'Donoghue
2026-09-17 0:05 ` sashiko-bot [this message]
2026-09-23 8:29 ` Krzysztof Kozlowski
2026-09-16 23:58 ` [PATCH v18 2/2] phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver Bryan O'Donoghue
2026-09-17 0:08 ` sashiko-bot
2026-09-22 12:15 ` Neil Armstrong
2026-09-22 13:15 ` Manivannan Sadhasivam
2026-09-23 12:35 ` [PATCH v18 0/2] " Vinod Koul
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=20260917000537.EB7241F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=media-ci@linuxtv.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