Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Taniya Das" <taniya.das@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org
Subject: Re: [PATCH v4 5/7] clk: qcom: gpucc: Add GPU Clock Controller driver for Eliza
Date: Thu, 14 May 2026 10:26:10 +0000	[thread overview]
Message-ID: <20260514102611.14A69C2BCC9@smtp.kernel.org> (raw)
In-Reply-To: <20260513-eliza_mm_cc_v2-v4-5-e61b5434e8d9@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Duplicate clock definitions for the same hardware register and bit (gpu_cc_gpu_smmu_vote_clk and gpu_cc_hlos1_vote_gpu_smmu_clk).
--

commit 6d648a0e43468c77f650349682c80884c4151795
Author: Taniya Das <taniya.das@oss.qualcomm.com>

clk: qcom: gpucc: Add GPU Clock Controller driver for Eliza

This commit adds the Graphics Clock Controller (GPUCC) driver for the Eliza
platform, providing clock, reset, and GDSC definitions.

> diff --git a/drivers/clk/qcom/gpucc-eliza.c b/drivers/clk/qcom/gpucc-eliza.c
> new file mode 100644
> index 0000000000000..85ae0ab118405
> --- /dev/null
> +++ b/drivers/clk/qcom/gpucc-eliza.c

[ ... ]

> +static struct clk_branch gpu_cc_gpu_smmu_vote_clk = {
> +	.halt_reg = 0x7000,
> +	.halt_check = BRANCH_HALT_VOTED,
> +	.clkr = {
> +		.enable_reg = 0x7000,
> +		.enable_mask = BIT(0),
> +		.hw.init = &(const struct clk_init_data) {
> +			.name = "gpu_cc_gpu_smmu_vote_clk",
> +			.ops = &clk_branch2_ops,
> +		},
> +	},
> +};
> +
> +static struct clk_branch gpu_cc_hlos1_vote_gpu_smmu_clk = {
> +	.halt_reg = 0x7000,
> +	.halt_check = BRANCH_HALT_VOTED,
> +	.clkr = {
> +		.enable_reg = 0x7000,
> +		.enable_mask = BIT(0),
> +		.hw.init = &(const struct clk_init_data) {
> +			.name = "gpu_cc_hlos1_vote_gpu_smmu_clk",
> +			.ops = &clk_branch2_ops,
> +		},
> +	},
> +};

Both gpu_cc_gpu_smmu_vote_clk and gpu_cc_hlos1_vote_gpu_smmu_clk map to the
exact same hardware register (0x7000) and enable mask (BIT(0)).

Because the Common Clock Framework maintains independent reference counts and
state for each clock object, if one consumer disables its clock, won't CCF
clear BIT(0) in register 0x7000?

Could this abruptly shut down the SMMU clock in hardware even if the other
consumer's reference count is still active?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260513-eliza_mm_cc_v2-v4-0-e61b5434e8d9@oss.qualcomm.com?part=5

  reply	other threads:[~2026-05-14 10:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 15:27 [PATCH v4 0/7] Add support for Video, Camera, Graphics clock controllers on Eliza Taniya Das
2026-05-13 15:27 ` [PATCH v4 1/7] dt-bindings: clock: qcom: Add video clock controller on Qualcomm Eliza SoC Taniya Das
2026-05-14 10:18   ` Krzysztof Kozlowski
2026-05-14 10:21     ` Taniya Das
2026-05-13 15:27 ` [PATCH v4 2/7] dt-bindings: clock: qcom: document the Eliza GPU Clock Controller Taniya Das
2026-05-13 15:27 ` [PATCH v4 3/7] dt-bindings: clock: qcom: Add support for CAMCC for Eliza Taniya Das
2026-05-14  7:47   ` sashiko-bot
2026-05-13 15:27 ` [PATCH v4 4/7] clk: qcom: videocc: Add video clock controller driver " Taniya Das
2026-05-14  9:12   ` sashiko-bot
2026-05-13 15:27 ` [PATCH v4 5/7] clk: qcom: gpucc: Add GPU Clock Controller " Taniya Das
2026-05-14 10:26   ` sashiko-bot [this message]
2026-05-13 15:27 ` [PATCH v4 6/7] clk: qcom: camcc: Add support for camera clock controller " Taniya Das
2026-05-14 11:16   ` sashiko-bot
2026-05-13 15:27 ` [PATCH v4 7/7] arm64: dts: qcom: eliza: Add support for MM clock controllers Taniya Das
2026-05-14 11:40   ` sashiko-bot

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=20260514102611.14A69C2BCC9@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