linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Marko <robimarko@gmail.com>
To: agross@kernel.org, bjorn.andersson@linaro.org,
	konrad.dybcio@somainline.org, mturquette@baylibre.com,
	sboyd@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, sivaprak@codeaurora.org,
	dmitry.baryshkov@linaro.org, linux-arm-msm@vger.kernel.org,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: Robert Marko <robimarko@gmail.com>
Subject: [PATCH v3 3/9] clk: qcom: apss-ipq6018: mark apcs_alias0_core_clk as critical
Date: Fri, 19 Aug 2022 00:06:22 +0200	[thread overview]
Message-ID: <20220818220628.339366-3-robimarko@gmail.com> (raw)
In-Reply-To: <20220818220628.339366-1-robimarko@gmail.com>

While fixing up the driver I noticed that my IPQ8074 board was hanging
after CPUFreq switched the frequency during boot, WDT would eventually
reset it.

So mark apcs_alias0_core_clk as critical since its the clock feeding the
CPU cluster and must never be disabled.

Fixes: 5e77b4ef1b19 ("clk: qcom: Add ipq6018 apss clock controller")
Signed-off-by: Robert Marko <robimarko@gmail.com>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
---
 drivers/clk/qcom/apss-ipq6018.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/clk/qcom/apss-ipq6018.c b/drivers/clk/qcom/apss-ipq6018.c
index be952d417ded..f2f502e2d5a4 100644
--- a/drivers/clk/qcom/apss-ipq6018.c
+++ b/drivers/clk/qcom/apss-ipq6018.c
@@ -56,7 +56,7 @@ static struct clk_branch apcs_alias0_core_clk = {
 			.parent_hws = (const struct clk_hw *[]){
 				&apcs_alias0_clk_src.clkr.hw },
 			.num_parents = 1,
-			.flags = CLK_SET_RATE_PARENT,
+			.flags = CLK_SET_RATE_PARENT | CLK_IS_CRITICAL,
 			.ops = &clk_branch2_ops,
 		},
 	},
-- 
2.37.2


  parent reply	other threads:[~2022-08-18 22:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 22:06 [PATCH v3 1/9] clk: qcom: clk-rcg2: add rcg2 mux ops Robert Marko
2022-08-18 22:06 ` [PATCH v3 2/9] clk: qcom: apss-ipq6018: fix apcs_alias0_clk_src Robert Marko
2022-08-18 22:06 ` Robert Marko [this message]
2022-08-18 22:06 ` [PATCH v3 4/9] dt-bindings: clock: qcom,a53pll: add IPQ8074 compatible Robert Marko
2022-08-18 22:06 ` [PATCH v3 5/9] clk: qcom: apss-ipq-pll: use OF match data for Alpha PLL config Robert Marko
2022-08-18 22:06 ` [PATCH v3 6/9] clk: qcom: apss-ipq-pll: update IPQ6018 " Robert Marko
2022-08-18 22:06 ` [PATCH v3 7/9] clk: qcom: apss-ipq-pll: add support for IPQ8074 Robert Marko
2022-08-18 22:06 ` [PATCH v3 8/9] arm64: dts: qcom: ipq8074: correct APCS register space size Robert Marko
2022-08-18 22:06 ` [PATCH v3 9/9] arm64: dts: qcom: ipq8074: add A53 PLL node Robert Marko
2022-10-18  3:14 ` (subset) [PATCH v3 1/9] clk: qcom: clk-rcg2: add rcg2 mux ops Bjorn Andersson

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=20220818220628.339366-3-robimarko@gmail.com \
    --to=robimarko@gmail.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@somainline.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=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sivaprak@codeaurora.org \
    /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;
as well as URLs for NNTP newsgroup(s).