From: sashiko-bot@kernel.org
To: "Taniya Das" <taniya.das@oss.qualcomm.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v9 06/10] dt-bindings: clock: qcom: Add support for CAMCC for Eliza
Date: Tue, 04 Aug 2026 18:29:25 +0000 [thread overview]
Message-ID: <20260804182926.71E981F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260804-eliza-mm-cc-v9-v9-6-39067760dc3c@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The binding unconditionally requires `#power-domain-cells` for all compatibles, incorrectly forcing the BIST MCLK controller (`qcom,eliza-cambistmclkcc`) to act as a power domain provider.
--
--- Patch [6]: [PATCH v9 06/10] dt-bindings: clock: qcom: Add support for CAMCC for Eliza ---
commit 3b7afe439852001ef758258be71850042fc0ea32
Author: Taniya Das <taniya.das@oss.qualcomm.com>
dt-bindings: clock: qcom: Add support for CAMCC for Eliza
This commit adds compatible strings for the Eliza camera and camera BIST
clock controllers to the Milos camcc binding. It also includes new header
files for the clocks and modifies the schema to require the
#power-domain-cells property.
> diff --git a/Documentation/devicetree/bindings/clock/qcom,milos-camcc.yaml b/Documentation/devicetree/bindings/clock/qcom,milos-camcc.yaml
> index c4aba40e316ca..cf7df47acbe7f 100644
> --- a/Documentation/devicetree/bindings/clock/qcom,milos-camcc.yaml
> +++ b/Documentation/devicetree/bindings/clock/qcom,milos-camcc.yaml
[ ... ]
> @@ -8,16 +8,23 @@ title: Qualcomm Camera Clock & Reset Controller on Milos
>
> maintainers:
> - Luca Weiss <luca.weiss@fairphone.com>
> + - Taniya Das <taniya.das@oss.qualcomm.com>
>
> description: |
> Qualcomm camera clock control module provides the clocks, resets and power
> domains on Milos.
>
> - See also: include/dt-bindings/clock/qcom,milos-camcc.h
> + See also:
> + include/dt-bindings/clock/qcom,eliza-cambistmclkcc.h
> + include/dt-bindings/clock/qcom,eliza-camcc.h
> + include/dt-bindings/clock/qcom,milos-camcc.h
>
> properties:
> compatible:
> - const: qcom,milos-camcc
> + enum:
> + - qcom,eliza-cambistmclkcc
> + - qcom,eliza-camcc
> + - qcom,milos-camcc
>
> clocks:
> items:
[ ... ]
> @@ -44,6 +51,7 @@ required:
> - clocks
> - power-domains
> - required-opps
> + - '#power-domain-cells'
[Severity: Medium]
Does adding #power-domain-cells to the global required properties force
the qcom,eliza-cambistmclkcc hardware to incorrectly act as a power domain
provider?
Looking at the new header include/dt-bindings/clock/qcom,eliza-cambistmclkcc.h,
the BIST MCLK controller appears to define only clocks, lacking any power
domains or resets.
Because #power-domain-cells is now unconditionally required here, will a
device tree node for the BIST controller fail dtbs_check if it accurately
omits the #power-domain-cells property? Would it be appropriate to isolate
the unique constraints for qcom,eliza-cambistmclkcc using a conditional block?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260804-eliza-mm-cc-v9-v9-0-39067760dc3c@oss.qualcomm.com?part=6
next prev parent reply other threads:[~2026-08-04 18:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 17:50 [PATCH v9 00/10] Add support for Video, Camera, Graphics clock controllers on Eliza Taniya Das
2026-08-04 17:50 ` [PATCH v9 01/10] dt-bindings: clock: qcom,milos-camcc: Add missing power-domains support Taniya Das
2026-08-04 17:50 ` [PATCH v9 02/10] dt-bindings: clock: qcom,milos-videocc: " Taniya Das
2026-08-04 17:50 ` [PATCH v9 03/10] arm64: dts: qcom: milos: Add power-domains for camcc and videocc Taniya Das
2026-08-05 13:42 ` Abel Vesa
2026-08-04 17:50 ` [PATCH v9 04/10] dt-bindings: clock: qcom: Add video clock controller on Qualcomm Eliza SoC Taniya Das
2026-08-04 17:50 ` [PATCH v9 05/10] dt-bindings: clock: qcom: document the Eliza GPU Clock Controller Taniya Das
2026-08-04 17:50 ` [PATCH v9 06/10] dt-bindings: clock: qcom: Add support for CAMCC for Eliza Taniya Das
2026-08-04 18:29 ` sashiko-bot [this message]
2026-08-05 14:26 ` Rob Herring
2026-08-06 9:58 ` Taniya Das
2026-08-04 17:50 ` [PATCH v9 07/10] clk: qcom: videocc: Add video clock controller driver " Taniya Das
2026-08-04 17:50 ` [PATCH v9 08/10] clk: qcom: gpucc: Add GPU Clock Controller " Taniya Das
2026-08-05 13:40 ` Abel Vesa
2026-08-04 17:50 ` [PATCH v9 09/10] clk: qcom: camcc: Add support for camera clock controller " Taniya Das
2026-08-04 18:57 ` sashiko-bot
2026-08-04 17:50 ` [PATCH v9 10/10] arm64: dts: qcom: eliza: Add support for MM clock controllers 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=20260804182926.71E981F000E9@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