From: Imran Shaik <quic_imrashai@quicinc.com>
To: Taniya Das <quic_tdas@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>
Cc: Ajit Pandey <quic_ajipan@quicinc.com>,
Jagadeesh Kona <quic_jkona@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] clk: qcom: gdsc: Set retain_ff before moving to HW CTRL
Date: Tue, 18 Feb 2025 12:33:45 +0530 [thread overview]
Message-ID: <7834c2e5-8c0a-4223-abfb-e21ae82d9e0a@quicinc.com> (raw)
In-Reply-To: <20250214-gdsc_fixes-v1-1-73e56d68a80f@quicinc.com>
On 2/14/2025 9:56 AM, Taniya Das wrote:
> Enable the retain_ff_enable bit of GDSCR only if the GDSC is already ON.
> Once the GDSCR moves to HW control, SW no longer can determine the state
> of the GDSCR and setting the retain_ff bit could destroy all the register
> contents we intended to save.
> Therefore, move the retain_ff configuration before switching the GDSC to
> HW trigger mode.
>
> Cc: stable@vger.kernel.org
> Fixes: 173722995cdb ("clk: qcom: gdsc: Add support to enable retention of GSDCR")
> Signed-off-by: Taniya Das <quic_tdas@quicinc.com>
> ---
> drivers/clk/qcom/gdsc.c | 21 +++++++++++----------
> 1 file changed, 11 insertions(+), 10 deletions(-)
>
Reviewed-by: Imran Shaik <quic_imrashai@quicinc.com>
Tested-by: Imran Shaik <quic_imrashai@quicinc.com> # on QCS8300
next prev parent reply other threads:[~2025-02-18 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 4:26 [PATCH 0/2] clk: qcom: gdsc: Update retain_ff sequence and timeout for GDSC Taniya Das
2025-02-14 4:26 ` [PATCH 1/2] clk: qcom: gdsc: Set retain_ff before moving to HW CTRL Taniya Das
2025-02-18 7:03 ` Imran Shaik [this message]
2025-02-14 4:27 ` [PATCH 2/2] clk: qcom: gdsc: Update the status poll timeout for GDSC Taniya Das
2025-02-18 7:03 ` Imran Shaik
2025-03-14 20:01 ` [PATCH 0/2] clk: qcom: gdsc: Update retain_ff sequence and " 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=7834c2e5-8c0a-4223-abfb-e21ae82d9e0a@quicinc.com \
--to=quic_imrashai@quicinc.com \
--cc=andersson@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=quic_ajipan@quicinc.com \
--cc=quic_jkona@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=sboyd@kernel.org \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®