On 2019-02-26 4:24 p.m., Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v4.20.12, v4.19.25, v4.1
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v4.20.12, v4.19.25, v4.14.103,
v4.9.160, v4.4.176, v3.18.136.
v4.20.12: Build OK!
On Fri, Feb 22, 2019 at 10:39 AM Harry Wentland wrote:
>
> Powerplay functions called from dm_pp_* functions tend to do a
> mutex_lock which isn't safe to do inside a kernel_fpu_begin/end block as
> those will disable/enable preemption.
>
> Rearrange the dm_pp_get_clock_levels_by_type_with_voltage
Acked-by: Alex Deucher
From: amd-gfx on behalf of Harry
Wentland
Sent: Friday, February 22, 2019 10:39 AM
To: amd-gfx@lists.freedesktop.org
Cc: robdcl...@gmail.com; Wentland, Harry; sta...@vger.kernel.org
Subject: [PATCH] drm/amd/display: don't call d
Powerplay functions called from dm_pp_* functions tend to do a
mutex_lock which isn't safe to do inside a kernel_fpu_begin/end block as
those will disable/enable preemption.
Rearrange the dm_pp_get_clock_levels_by_type_with_voltage calls to make
sure they happen outside of kernel_fpu_begin/end.
C
