From: sashiko-bot@kernel.org
To: "Taniya Das" <taniya.das@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 1/7] dt-bindings: clock: qcom: Add video clock controller on Qualcomm Eliza SoC
Date: Thu, 14 May 2026 05:33:39 +0000 [thread overview]
Message-ID: <20260514053340.4DE4EC2BCB7@smtp.kernel.org> (raw)
In-Reply-To: <20260513-eliza_mm_cc_v2-v3-1-b59c370dc281@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The schema does not define the `power-domains` property, preventing valid device trees from describing the hardware correctly.
--
commit b3d73d9e0090a370ecfafe8774b6d58d6907b4db
Author: Taniya Das <taniya.das@oss.qualcomm.com>
dt-bindings: clock: qcom: Add video clock controller on Qualcomm Eliza SoC
This commit adds the Eliza video clock controller compatible string to the
existing Milos videocc binding. It also includes the corresponding
dt-bindings header for Eliza.
> Eliza Video clock controller is on CX and MX rails similar to Milos.
Since the commit message explicitly states the hardware is on the CX and MX
rails, shouldn't the power-domains property be defined in the binding?
> diff --git a/Documentation/devicetree/bindings/clock/qcom,milos-videocc.yaml b/Documentation/devicetree/bindings/clock/qcom,milos-videocc.yaml
> index 14c31efe1308a..6e3e4424af78a 100644
> --- a/Documentation/devicetree/bindings/clock/qcom,milos-videocc.yaml
> +++ b/Documentation/devicetree/bindings/clock/qcom,milos-videocc.yaml
[ ... ]
> properties:
> compatible:
> - const: qcom,milos-videocc
> + enum:
> + - qcom,eliza-videocc
> + - qcom,milos-videocc
>
> clocks:
The schema qcom,milos-videocc.yaml does not define the power-domains property,
and neither does its referenced schemas. Since the schema uses
unevaluatedProperties: false, any device tree node that correctly specifies
the power-domains property to model this hardware dependency will fail schema
validation.
This forces developers to omit the property from the device tree entirely. If
the required CX/MX power rails are not incidentally enabled by another
consumer, accessing the unpowered video clock controller registers during
probe or runtime could cause a synchronous external abort and kernel panic.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260513-eliza_mm_cc_v2-v3-0-b59c370dc281@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-05-14 5:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 14:23 [PATCH v3 0/7] Add support for Video, Camera, Graphics clock controllers on Eliza Taniya Das
2026-05-13 14:23 ` [PATCH v3 1/7] dt-bindings: clock: qcom: Add video clock controller on Qualcomm Eliza SoC Taniya Das
2026-05-14 5:33 ` sashiko-bot [this message]
2026-05-13 14:23 ` [PATCH v3 2/7] dt-bindings: clock: qcom: document the Eliza GPU Clock Controller Taniya Das
2026-05-13 14:23 ` [PATCH v3 3/7] dt-bindings: clock: qcom: Add support for CAMCC for Eliza Taniya Das
2026-05-14 6:04 ` sashiko-bot
2026-05-13 14:23 ` [PATCH v3 4/7] clk: qcom: videocc: Add video clock controller driver " Taniya Das
2026-05-13 14:23 ` [PATCH v3 5/7] clk: qcom: gpucc: Add GPU Clock Controller " Taniya Das
2026-05-14 10:02 ` sashiko-bot
2026-05-13 14:23 ` [PATCH v3 6/7] clk: qcom: camcc: Add support for camera clock controller " Taniya Das
2026-05-14 11:01 ` sashiko-bot
2026-05-13 14:23 ` [PATCH v3 7/7] arm64: dts: qcom: eliza: Add support for MM clock controllers Taniya Das
2026-05-14 11:18 ` sashiko-bot
2026-05-13 15:29 ` [PATCH v3 0/7] Add support for Video, Camera, Graphics clock controllers on Eliza Taniya Das
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=20260514053340.4DE4EC2BCB7@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@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