mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Brian Masney <bmasney@redhat.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Taniya Das <taniya.das@oss.qualcomm.com>
Subject: Re: [PATCH] clk: qcom: enable ALWAYS_ON for titan_top_gdsc
Date: Wed, 1 Jul 2026 09:37:04 +0530	[thread overview]
Message-ID: <56ebd97b-0834-41ac-8fdb-2469e2848694@oss.qualcomm.com> (raw)
In-Reply-To: <bcf9fd99-454f-4ac2-8357-b0775be42d41@oss.qualcomm.com>



On 6/26/2026 10:02 PM, Konrad Dybcio wrote:
> On 6/26/26 6:26 PM, Brian Masney wrote:
>> With the introduction of sync_state support in the clk and pmdomain
>> subsystems, the following warning happens when the unused clocks are
>> shutdown in camcc-sc8280xp:
> 
> Stuck at _on_ sounds wrong.. does clk_ignore_unused / removing
> the sync state from the clock part only resolve this? There may
> be a clock dependency for the TITAN_TOP_GDSC that we're failing to
> describe
> 

Hi Brian,

This probably could be due to camcc_gdsc_clk getting turned OFF during the
sync_state, but this clk is required for GDSC transitions. The camcc_gdsc_clk
is currently kept always ON from probe in camcc-sc8280xp, but the clock is
also modeled with clock framework, so the clock can get disabled in sync_state
callback now.

Can you please try removing the modelling of camcc_gdsc_clk using below diff
and see if helps here?


diff --git a/drivers/clk/qcom/camcc-sc8280xp.c b/drivers/clk/qcom/camcc-sc8280xp.c
index e97b8d4f3c84..660d8655d391 100644
--- a/drivers/clk/qcom/camcc-sc8280xp.c
+++ b/drivers/clk/qcom/camcc-sc8280xp.c
@@ -1753,24 +1753,6 @@ static struct clk_branch camcc_csiphy3_clk = {
        },
 };

-static struct clk_branch camcc_gdsc_clk = {
-       .halt_reg = 0xc1e4,
-       .halt_check = BRANCH_HALT,
-       .clkr = {
-               .enable_reg = 0xc1e4,
-               .enable_mask = BIT(0),
-               .hw.init = &(struct clk_init_data){
-                       .name = "camcc_gdsc_clk",
-                       .parent_hws = (const struct clk_hw*[]){
-                               &camcc_xo_clk_src.clkr.hw,
-                       },
-                       .num_parents = 1,
-                       .flags = CLK_SET_RATE_PARENT,
-                       .ops = &clk_branch2_ops,
-               },
-       },
-};
-
 static struct clk_branch camcc_icp_ahb_clk = {
        .halt_reg = 0xc0d8,
        .halt_check = BRANCH_HALT,
@@ -2839,7 +2821,6 @@ static struct clk_regmap *camcc_sc8280xp_clocks[] = {
        [CAMCC_CSIPHY2_CLK] = &camcc_csiphy2_clk.clkr,
        [CAMCC_CSIPHY3_CLK] = &camcc_csiphy3_clk.clkr,
        [CAMCC_FAST_AHB_CLK_SRC] = &camcc_fast_ahb_clk_src.clkr,
-       [CAMCC_GDSC_CLK] = &camcc_gdsc_clk.clkr,
        [CAMCC_ICP_AHB_CLK] = &camcc_icp_ahb_clk.clkr,
        [CAMCC_ICP_CLK] = &camcc_icp_clk.clkr,
        [CAMCC_ICP_CLK_SRC] = &camcc_icp_clk_src.clkr,


Thanks,
Jagadeesh


  parent reply	other threads:[~2026-07-01  4:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26 16:26 Brian Masney
2026-06-26 16:32 ` Konrad Dybcio
2026-06-26 16:54   ` Vladimir Zapolskiy
2026-06-29 11:03     ` Brian Masney
2026-06-29 13:00       ` Vladimir Zapolskiy
2026-06-29 15:27         ` Brian Masney
2026-06-29 16:29           ` Vladimir Zapolskiy
2026-07-01  4:07   ` Jagadeesh Kona [this message]
2026-07-01 14:09     ` Brian Masney
2026-06-26 16:59 ` Vladimir Zapolskiy
2026-06-29 11:07   ` Brian Masney
2026-06-27  9:51 ` Bryan O'Donoghue
2026-06-29 11:01   ` Brian Masney

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=56ebd97b-0834-41ac-8fdb-2469e2848694@oss.qualcomm.com \
    --to=jagadeesh.kona@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=bmasney@redhat.com \
    --cc=bryan.odonoghue@linaro.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --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

all inboxes | Powered by JetHome®