Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Taniya Das" <taniya.das@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v10 10/10] arm64: dts: qcom: eliza: Add support for MM clock controllers
Date: Thu, 06 Aug 2026 10:47:01 +0000	[thread overview]
Message-ID: <20260806104701.EDD701F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260806-eliza-mm-cc-v9-v10-10-6ba52dd14343@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Device tree nodes for gpucc, videocc, and camcc are inserted out of unit-address sorting order.
--

--- Patch [10]: [PATCH v10 10/10] arm64: dts: qcom: eliza: Add support for MM clock controllers ---
commit 1e9fc02b64bc332e46fe1a0e852faed44bcbabfb
Author: Taniya Das <taniya.das@oss.qualcomm.com>

arm64: dts: qcom: eliza: Add support for MM clock controllers

Add the device nodes for the multimedia clock controllers (cambistmclkcc,
camcc, videocc, gpucc) for Qualcomm Eliza SoC.

> diff --git a/arch/arm64/boot/dts/qcom/eliza.dtsi b/arch/arm64/boot/dts/qcom/eliza.dtsi
> index 66ea4aaafd73a..94297e05677ae 100644
> --- a/arch/arm64/boot/dts/qcom/eliza.dtsi
> +++ b/arch/arm64/boot/dts/qcom/eliza.dtsi
[ ... ]
> @@ -2893,6 +2914,60 @@ mdss_dp0_out: endpoint {
>  			};
>  		};
>  
> +		gpucc: clock-controller@3d90000 {

[Severity: Low]
Are the newly added nodes (gpucc@3d90000, videocc@aaf0000, camcc@ade0000)
inserted out of unit-address sorting order here?

They appear to be placed after the mdss@ae00000 node which has a higher unit
address. Does this violate the device tree convention requiring child nodes
to be sorted by unit address in ascending order?

> +			compatible = "qcom,eliza-gpucc";
> +			reg = <0x0 0x03d90000 0x0 0xa000>;
> +
> +			clocks = <&bi_tcxo_div2>,
> +				 <&gcc GCC_GPU_GPLL0_CPH_CLK_SRC>,
> +				 <&gcc GCC_GPU_GPLL0_DIV_CPH_CLK_SRC>;
> +
> +			power-domains = <&rpmhpd RPMHPD_MX>,
> +					<&rpmhpd RPMHPD_CX>;
> +			required-opps = <&rpmhpd_opp_low_svs>,
> +					<&rpmhpd_opp_low_svs>;
> +			#clock-cells = <1>;
> +			#reset-cells = <1>;
> +			#power-domain-cells = <1>;
> +		};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260806-eliza-mm-cc-v9-v10-0-6ba52dd14343@oss.qualcomm.com?part=10

      reply	other threads:[~2026-08-06 10:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 10:34 [PATCH v10 00/10] Add support for Video, Camera, Graphics clock controllers on Eliza Taniya Das
2026-08-06 10:34 ` [PATCH v10 01/10] dt-bindings: clock: qcom,milos-camcc: Add missing power-domains support Taniya Das
2026-08-06 10:34 ` [PATCH v10 02/10] dt-bindings: clock: qcom,milos-videocc: " Taniya Das
2026-08-06 10:34 ` [PATCH v10 03/10] arm64: dts: qcom: milos: Add power-domains for camcc and videocc Taniya Das
2026-08-06 10:34 ` [PATCH v10 04/10] dt-bindings: clock: qcom: Add video clock controller on Qualcomm Eliza SoC Taniya Das
2026-08-06 10:34 ` [PATCH v10 05/10] dt-bindings: clock: qcom: document the Eliza GPU Clock Controller Taniya Das
2026-08-06 10:34 ` [PATCH v10 06/10] dt-bindings: clock: qcom: Add support for CAMCC for Eliza Taniya Das
2026-08-06 10:48   ` sashiko-bot
2026-08-06 10:34 ` [PATCH v10 07/10] clk: qcom: videocc: Add video clock controller driver " Taniya Das
2026-08-06 10:34 ` [PATCH v10 08/10] clk: qcom: gpucc: Add GPU Clock Controller " Taniya Das
2026-08-06 10:34 ` [PATCH v10 09/10] clk: qcom: camcc: Add support for camera clock controller " Taniya Das
2026-08-06 10:56   ` sashiko-bot
2026-08-06 10:34 ` [PATCH v10 10/10] arm64: dts: qcom: eliza: Add support for MM clock controllers Taniya Das
2026-08-06 10:47   ` sashiko-bot [this message]

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=20260806104701.EDD701F000E9@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