public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Taniya Das <quic_tdas@quicinc.com>,
	David Wronek <davidwronek@gmail.com>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Taniya Das <tdas@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	phone-devel@vger.kernel.org, map220v <map220v300@gmail.com>
Subject: Re: [PATCH 4/7] clk: qcom: gcc-sc7180: Fix up gcc_sdcc2_apps_clk_src
Date: Wed, 5 Jul 2023 12:45:36 +0200	[thread overview]
Message-ID: <ae5a09e7-d008-0123-ab66-8f0806ad1c19@linaro.org> (raw)
In-Reply-To: <9f06d400-be7b-6806-b055-8cc7f11db6ca@quicinc.com>

On 5.07.2023 06:27, Taniya Das wrote:
> 
> 
> On 7/4/2023 10:01 PM, David Wronek wrote:
>> From: map220v <map220v300@gmail.com>
>>
>> Add the PARENT_ENABLE flag to prevent the clock from getting stuck at
>> boot.
>>
>> Fixes: 17269568f726 ("clk: qcom: Add Global Clock controller (GCC) driver for SC7180")
>> Signed-off-by: map220v <map220v300@gmail.com>
>> Signed-off-by: David Wronek <davidwronek@gmail.com>
>> ---
>>   drivers/clk/qcom/gcc-sc7180.c | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/clk/qcom/gcc-sc7180.c b/drivers/clk/qcom/gcc-sc7180.c
>> index cef3c77564cf..49f36e1df4fa 100644
>> --- a/drivers/clk/qcom/gcc-sc7180.c
>> +++ b/drivers/clk/qcom/gcc-sc7180.c
>> @@ -651,6 +651,7 @@ static struct clk_rcg2 gcc_sdcc2_apps_clk_src = {
>>           .name = "gcc_sdcc2_apps_clk_src",
>>           .parent_data = gcc_parent_data_5,
>>           .num_parents = ARRAY_SIZE(gcc_parent_data_5),
>> +        .flags = CLK_OPS_PARENT_ENABLE,
> 
> Could you please share what Stuck warnings are you observing?
My educated guess would be that the max frequency uses GPLL7, which
is either not enabled by default, or is shut down by unused clk
cleanup down the pipe.

Konrad
> 
>>           .ops = &clk_rcg2_floor_ops,
>>       },
>>   };
> 

  reply	other threads:[~2023-07-05 10:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 16:31 [PATCH 0/7] Add initial support for SM7125 and Xiaomi SM7125 platform David Wronek
2023-07-04 16:31 ` [PATCH 1/7] dt-bindings: arm: qcom,ids: Add SoC ID for SM7125 David Wronek
2023-07-05  9:46   ` Krzysztof Kozlowski
2023-07-05 15:48     ` David Wronek
2023-07-06  6:09       ` Krzysztof Kozlowski
2023-07-04 16:31 ` [PATCH 2/7] dt-bindings: arm: qcom: Document SM7125 and xiaomi,joyeuse board David Wronek
2023-07-05  9:47   ` Krzysztof Kozlowski
2023-07-04 16:31 ` [PATCH 3/7] soc: qcom: socinfo: Add SoC ID for SM7125 David Wronek
2023-07-04 16:31 ` [PATCH 4/7] clk: qcom: gcc-sc7180: Fix up gcc_sdcc2_apps_clk_src David Wronek
2023-07-05  4:27   ` Taniya Das
2023-07-05 10:45     ` Konrad Dybcio [this message]
2023-07-05 13:41     ` ungeskriptet
2023-07-05  9:48   ` Krzysztof Kozlowski
2023-07-04 16:31 ` [PATCH 5/7] arm64: dts: qcom: pm6150: Add resin and rtc nodes David Wronek
2023-07-04 18:06   ` Konrad Dybcio
2023-07-04 16:31 ` [PATCH 6/7] arm64: dts: qcom: Add SM7125 device tree David Wronek
2023-07-05  9:50   ` Krzysztof Kozlowski
2023-07-04 16:32 ` [PATCH 7/7] arm64: dts: qcom: Add support for the Xiaomi SM7125 platform David Wronek
2023-07-04 18:10   ` Konrad Dybcio
2023-07-05  9:54   ` Krzysztof Kozlowski

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=ae5a09e7-d008-0123-ab66-8f0806ad1c19@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=davidwronek@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=map220v300@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=quic_tdas@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=tdas@codeaurora.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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