From: Sasha Levin <sashal@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 5.11 26/52] clk: qcom: gdsc: Implement NO_RET_PERIPH flag
Date: Thu, 4 Mar 2021 16:30:42 -0500 [thread overview]
Message-ID: <YEFRgsJr4qwxbpTO@sashalap> (raw)
In-Reply-To: <161472614572.1254594.7093847798808554286@swboyd.mtv.corp.google.com>
On Tue, Mar 02, 2021 at 03:02:25PM -0800, Stephen Boyd wrote:
>Quoting Sasha Levin (2021-03-02 03:55:07)
>> From: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
>>
>> [ Upstream commit 785c02eb35009a4be6dbc68f4f7d916e90b7177d ]
>>
>> In some rare occasions, we want to only set the RETAIN_MEM bit, but
>> not the RETAIN_PERIPH one: this is seen on at least SDM630/636/660's
>> GPU-GX GDSC, where unsetting and setting back the RETAIN_PERIPH bit
>> will generate chaos and panics during GPU suspend time (mainly, the
>> chaos is unaligned access).
>>
>> For this reason, introduce a new NO_RET_PERIPH flag to the GDSC
>> driver to address this corner case.
>
>Is there a patch that's going to use this in stable trees? On its own
>this patch doesn't make sense to backport.
Right, I'll also grab a59c16c80bd7 ("clk: qcom: gpucc-msm8998: Add
resets, cxc, fix flags on gpu_gx_gdsc") for 5.10 and 5.11. Thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2021-03-04 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210302115534.61800-1-sashal@kernel.org>
2021-03-02 11:55 ` [PATCH AUTOSEL 5.11 26/52] clk: qcom: gdsc: Implement NO_RET_PERIPH flag Sasha Levin
2021-03-02 23:02 ` Stephen Boyd
2021-03-04 21:30 ` Sasha Levin [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=YEFRgsJr4qwxbpTO@sashalap \
--to=sashal@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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