diff options
author | Rafael J. Wysocki | 2019-02-14 23:46:19 +0100 |
---|---|---|
committer | Greg Kroah-Hartman | 2019-02-27 10:09:01 +0100 |
commit | 06fa186854113793456b0c4c2ba09471f5ec1362 (patch) | |
tree | 5c2df7db5bf6d08c3128da3cfdccc4c8e7c5e319 /drivers/gpu/drm/i915 | |
parent | drm/amdgpu: Set DPM_FLAG_NEVER_SKIP when enabling PM-runtime (diff) | |
download | kernel-qcow2-linux-06fa186854113793456b0c4c2ba09471f5ec1362.tar.gz kernel-qcow2-linux-06fa186854113793456b0c4c2ba09471f5ec1362.tar.xz kernel-qcow2-linux-06fa186854113793456b0c4c2ba09471f5ec1362.zip |
gpu: drm: radeon: Set DPM_FLAG_NEVER_SKIP when enabling PM-runtime
commit 450d007d199e632a1a4c4b91302deacd7d56815f upstream.
On HP ProBook 4540s, if PM-runtime is enabled in the radeon driver
and the direct-complete optimization is used for the radeon device
during system-wide suspend, the system doesn't resume.
Preventing direct-complete from being used with the radeon device by
setting the DPM_FLAG_NEVER_SKIP driver flag for it makes the problem
go away, which indicates that direct-complete is not safe for the
radeon driver in general and should not be used with it (at least
for now).
This fixes a regression introduced by commit c62ec4610c40
("PM / core: Fix direct_complete handling for devices with no
callbacks") which allowed direct-complete to be applied to
devices without PM callbacks (again) which in turn unlocked
direct-complete for radeon on HP ProBook 4540s.
Fixes: c62ec4610c40 ("PM / core: Fix direct_complete handling for devices with no callbacks")
Link: https://bugzilla.kernel.org/show_bug.cgi?id=201519
Reported-by: Ярослав Семченко <ukrkyi@gmail.com>
Tested-by: Ярослав Семченко <ukrkyi@gmail.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/gpu/drm/i915')
0 files changed, 0 insertions, 0 deletions