From: sashiko-bot@kernel.org
To: "Taniya Das" <taniya.das@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: clock: qcom: Add video clock controller on Nord SoC
Date: Mon, 06 Jul 2026 09:08:35 +0000 [thread overview]
Message-ID: <20260706090835.E38221F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260706-nord_videocc_camcc-v1-1-bae3be9e9770@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The new compatible string `qcom,nord-videocc` is added to the top-level `compatible` enum but is omitted from the `if-then` conditional block that enforces the `required-opps` property.
--
commit 3e90aae8332184ade41937f239c5a380bf14e445
Author: Taniya Das <taniya.das@oss.qualcomm.com>
dt-bindings: clock: qcom: Add video clock controller on Nord SoC
Add compatible string for Nord video clock controller and the bindings
for Nord Qualcomm SoC.
> diff --git a/Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml b/Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml
> index 5d77029bfaf88..9b9878e9b9cfc 100644
> --- a/Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml
> +++ b/Documentation/devicetree/bindings/clock/qcom,sm8450-videocc.yaml
[ ... ]
> @@ -27,6 +28,7 @@ properties:
> enum:
> - qcom,glymur-videocc
> - qcom,kaanapali-videocc
> + - qcom,nord-videocc
> - qcom,sm8450-videocc
> - qcom,sm8475-videocc
> - qcom,sm8550-videocc
[Severity: Medium]
Does qcom,nord-videocc also require the required-opps property like the other
compatible strings in this binding?
If so, is it a regression that this new compatible string was omitted from
the allOf conditional block that enforces it?
For instance, the existing conditional block enforces required-opps for the
other devices:
allOf:
- $ref: qcom,gcc.yaml#
- if:
properties:
compatible:
contains:
enum:
- qcom,glymur-videocc
- qcom,kaanapali-videocc
- qcom,sm8450-videocc
- qcom,sm8550-videocc
- qcom,sm8750-videocc
- qcom,x1p42100-videocc
then:
required:
- required-opps
Without updating this block, does this allow device trees missing
required-opps for qcom,nord-videocc to pass schema validation?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260706-nord_videocc_camcc-v1-0-bae3be9e9770@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-07-06 9:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 8:57 [PATCH 0/4] clk: qcom: Add video and camera clock controller support for Nord Taniya Das
2026-07-06 8:57 ` [PATCH 1/4] dt-bindings: clock: qcom: Add video clock controller on Nord SoC Taniya Das
2026-07-06 9:08 ` sashiko-bot [this message]
2026-07-06 8:57 ` [PATCH 2/4] dt-bindings: clock: qcom: Add support for Camera Clock Controller for Nord Taniya Das
2026-07-06 8:57 ` [PATCH 3/4] clk: qcom: videocc-nord: Add video clock controller driver " Taniya Das
2026-07-06 9:15 ` sashiko-bot
2026-07-06 12:17 ` Konrad Dybcio
2026-07-06 14:39 ` Dmitry Baryshkov
2026-07-06 8:57 ` [PATCH 4/4] clk: qcom: camcc: Add support for camera clock controller " Taniya Das
2026-07-06 13:07 ` Konrad Dybcio
2026-07-06 14:40 ` 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=20260706090835.E38221F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=taniya.das@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