From: patchwork-bot+linux-arm-msm@kernel.org
To: Taniya Das <tdas@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [v2 1/2] clk: qcom: gdsc: Add support to update GDSC transition delay
Date: Fri, 08 Apr 2022 13:37:29 +0000 [thread overview]
Message-ID: <164942504971.26125.7158383360196834147.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220223185606.3941-1-tdas@codeaurora.org>
Hello:
This series was applied to qcom/linux.git (for-next)
by Stephen Boyd <sboyd@kernel.org>:
On Thu, 24 Feb 2022 00:26:05 +0530 you wrote:
> GDSCs have multiple transition delays which are used for the GDSC FSM
> states. Older targets/designs required these values to be updated from
> gdsc code to certain default values for the FSM state to work as
> expected. But on the newer targets/designs the values updated from the
> GDSC driver can hamper the FSM state to not work as expected.
>
> On SC7180 we observe black screens because the gdsc is being
> enabled/disabled very rapidly and the GDSC FSM state does not work as
> expected. This is due to the fact that the GDSC reset value is being
> updated from SW.
>
> [...]
Here is the summary with links:
- [v2,1/2] clk: qcom: gdsc: Add support to update GDSC transition delay
https://git.kernel.org/qcom/c/4e7c4d3652f9
- [v2,2/2] clk: qcom: dispcc: Update the transition delay for MDSS GDSC
https://git.kernel.org/qcom/c/6e6fec3f961c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-04-08 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 18:56 [v2 1/2] clk: qcom: gdsc: Add support to update GDSC transition delay Taniya Das
2022-02-23 18:56 ` [v2 2/2] clk: qcom: dispcc: Update the transition delay for MDSS GDSC Taniya Das
2022-02-25 0:21 ` Stephen Boyd
2022-02-24 21:55 ` [v2 1/2] clk: qcom: gdsc: Add support to update GDSC transition delay Stephen Boyd
2022-02-25 0:21 ` Stephen Boyd
2022-04-08 13:37 ` patchwork-bot+linux-arm-msm [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=164942504971.26125.7158383360196834147.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=tdas@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