From: "Barnabás Czémán" <barnabas.czeman@mainlining.org>
To: "Bjorn Andersson" <andersson@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Sireesh Kodali" <sireeshkodali@protonmail.com>,
"Adam Skladowski" <a_skl39@protonmail.com>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Vladimir Lypak" <junak.pub@gmail.com>,
"Otto Pflüger" <otto.pflueger@abscue.de>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Barnabás Czémán" <barnabas.czeman@mainlining.org>
Subject: [PATCH 2/2] clk: qcom: gcc-msm8917: Remove ALWAYS_ON flag from cpp_gdsc
Date: Mon, 17 Nov 2025 18:58:48 +0100 [thread overview]
Message-ID: <20251117-fix-gdsc-cpp-msm8917-msm8953-v1-2-db33adcff28a@mainlining.org> (raw)
In-Reply-To: <20251117-fix-gdsc-cpp-msm8917-msm8953-v1-0-db33adcff28a@mainlining.org>
cpp_gdsc should not be always on, ALWAYS_ON flag was set accidentally.
Fixes: 33cc27a47d3a ("clk: qcom: Add global clock controller driver for MSM8917")
Signed-off-by: Barnabás Czémán <barnabas.czeman@mainlining.org>
---
drivers/clk/qcom/gcc-msm8917.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/clk/qcom/gcc-msm8917.c b/drivers/clk/qcom/gcc-msm8917.c
index 0a1aa623cd49..9d1c5a9953e2 100644
--- a/drivers/clk/qcom/gcc-msm8917.c
+++ b/drivers/clk/qcom/gcc-msm8917.c
@@ -3409,7 +3409,6 @@ static struct gdsc cpp_gdsc = {
.pd = {
.name = "cpp_gdsc",
},
- .flags = ALWAYS_ON,
.pwrsts = PWRSTS_OFF_ON,
};
--
2.51.2
next prev parent reply other threads:[~2025-11-17 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 17:58 [PATCH 0/2] MSM8917/MSM8953 " Barnabás Czémán
2025-11-17 17:58 ` [PATCH 1/2] clk: qcom: gcc-msm8953: " Barnabás Czémán
2025-11-18 9:33 ` Konrad Dybcio
2025-11-17 17:58 ` Barnabás Czémán [this message]
2025-11-18 9:33 ` [PATCH 2/2] clk: qcom: gcc-msm8917: " Konrad Dybcio
2026-01-07 18:38 ` [PATCH 0/2] MSM8917/MSM8953 " 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=20251117-fix-gdsc-cpp-msm8917-msm8953-v1-2-db33adcff28a@mainlining.org \
--to=barnabas.czeman@mainlining.org \
--cc=a_skl39@protonmail.com \
--cc=andersson@kernel.org \
--cc=junak.pub@gmail.com \
--cc=konradybcio@kernel.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=otto.pflueger@abscue.de \
--cc=sboyd@kernel.org \
--cc=sireeshkodali@protonmail.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®