linux-kernel - Re: [PATCH AUTOSEL 5.11 26/52] clk: qcom: gdsc: Implement NO_RET

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 4 Mar 2021 16:30:42 -0500
From:   Sasha Levin <sashal@...nel.org>
To:     Stephen Boyd <sboyd@...nel.org>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...ainline.org>,
        linux-clk@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 5.11 26/52] clk: qcom: gdsc: Implement
 NO_RET_PERIPH flag

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@...ainline.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