From: sashiko-bot@kernel.org
To: "Wenmeng Liu" <wenmeng.liu@oss.qualcomm.com>
Cc: robh@kernel.org, media-ci@linuxtv.org,
devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/6] dt-bindings: media: Add bindings for qcom,nord-camss
Date: Tue, 15 Sep 2026 09:45:45 +0000 [thread overview]
Message-ID: <20260915094546.404FD1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260915-nord-v1-1-20db41a7f1ff@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dt-bindings: media: Artificial limit of 5 CSI input ports in regex
--
commit ba64c074737d8584213f4eaf83a7f188c30698a0
Author: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
dt-bindings: media: Add bindings for qcom,nord-camss
This commit adds bindings for the camera subsystem (CAMSS) on the Qualcomm
Nord platform. The hardware introduces a significant number of blocks,
including 3 CSID and 10 CSID Lite receivers.
> diff --git a/Documentation/devicetree/bindings/media/qcom,nord-camss.yaml b/Documentation/devicetree/bindings/media/qcom,nord-camss.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/qcom,nord-camss.yaml
[ ... ]
> + ports:
> + $ref: /schemas/graph.yaml#/properties/ports
> +
> + description:
> + CSI input ports.
> +
> + patternProperties:
> + "^port@[0-4]$":
[Severity: Medium]
Does this regex artificially limit the allowed CSI input ports?
The commit message notes that the Nord CAMSS hardware exposes 13 CSID
receivers (3 CSID and 10 CSID Lite). However, restricting the ports block to
"^port@[0-4]$" limits the allowed ports to 5, preventing configuration of the
remaining 8 hardware receivers.
If a device tree attempts to map external PHYs to CSID ports 5 through 12,
won't it fail schema validation and drop the nodes from the parsed
configuration?
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + unevaluatedProperties: false
> +
> + description:
> + Input port for receiving CSI data.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260915-nord-v1-0-20db41a7f1ff@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-09-15 9:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 9:34 [PATCH 0/6] media: qcom: camss: Add support for Nord CAMSS Wenmeng Liu
2026-09-15 9:34 ` [PATCH 1/6] dt-bindings: media: Add bindings for qcom,nord-camss Wenmeng Liu
2026-09-15 9:45 ` sashiko-bot [this message]
2026-09-17 10:13 ` Krzysztof Kozlowski
2026-09-17 12:37 ` Wenmeng Liu
2026-09-18 6:47 ` Krzysztof Kozlowski
2026-09-18 7:08 ` Wenmeng Liu
2026-09-15 9:34 ` [PATCH 2/6] media: qcom: camss: csid: Add support for CSID 900 Wenmeng Liu
2026-09-15 9:50 ` sashiko-bot
2026-09-20 7:01 ` Shawn Guo
2026-09-15 9:34 ` [PATCH 3/6] media: qcom: camss: vfe: Add support for VFE gen4 Wenmeng Liu
2026-09-15 9:53 ` sashiko-bot
2026-09-20 7:19 ` Shawn Guo
2026-09-15 9:34 ` [PATCH 4/6] media: qcom: camss: vfe: Add support for VFE 900 Wenmeng Liu
2026-09-15 9:43 ` sashiko-bot
2026-09-20 7:17 ` Shawn Guo
2026-09-15 9:34 ` [PATCH 5/6] media: qcom: camss: tpg: Add support for TPG v2.5.0 Wenmeng Liu
2026-09-15 9:34 ` [PATCH 6/6] media: qcom: camss: Add support for nord camss Wenmeng Liu
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=20260915094546.404FD1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=media-ci@linuxtv.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wenmeng.liu@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