From: Bjorn Andersson <andersson@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Taniya Das <quic_tdas@quicinc.com>
Cc: Ajit Pandey <quic_ajipan@quicinc.com>,
Imran Shaik <quic_imrashai@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 0/2] clk: qcom: gdsc: Update retain_ff sequence and timeout for GDSC
Date: Fri, 14 Mar 2025 15:01:13 -0500 [thread overview]
Message-ID: <174198247873.1604753.9788641578266920775.b4-ty@kernel.org> (raw)
In-Reply-To: <20250214-gdsc_fixes-v1-0-73e56d68a80f@quicinc.com>
On Fri, 14 Feb 2025 09:56:58 +0530, Taniya Das wrote:
> The retain_ff bit should be updated for a GDSC when it is under SW
> control and ON. The current sequence needs to be fixed as the GDSC
> needs to update retention and is moved to HW control which does not
> guarantee the GDSC to be in enabled state.
>
> During the GDSC FSM state, the GDSC hardware waits for an ACK and the
> timeout for the ACK is 2000us as per design requirements.
>
> [...]
Applied, thanks!
[1/2] clk: qcom: gdsc: Set retain_ff before moving to HW CTRL
commit: 25708f73ff171bb4171950c9f4be5aa8504b8459
[2/2] clk: qcom: gdsc: Update the status poll timeout for GDSC
commit: 172320f5ead5d1a0eed14472ce84146221c75675
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2025-03-14 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 4:26 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
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 ` Bjorn Andersson [this message]
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=174198247873.1604753.9788641578266920775.b4-ty@kernel.org \
--to=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_imrashai@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®