Commit 450d007d authored by Rafael J. Wysocki's avatar Rafael J. Wysocki Committed by Alex Deucher

gpu: drm: radeon: Set DPM_FLAG_NEVER_SKIP when enabling PM-runtime

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 c62ec461
("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: c62ec461 ("PM / core: Fix direct_complete handling for devices with no callbacks")
Link: default avatarЯрослав Семченко <[email protected]>
Tested-by: default avatarЯрослав Семченко <[email protected]>
Signed-off-by: default avatarRafael J. Wysocki <[email protected]>
Signed-off-by: default avatarAlex Deucher <[email protected]>
Cc: [email protected]
parent a3b22b9f
......@@ -172,6 +172,7 @@ int radeon_driver_load_kms(struct drm_device *dev, unsigned long flags)
if (radeon_is_px(dev)) {
dev_pm_set_driver_flags(dev->dev, DPM_FLAG_NEVER_SKIP);
pm_runtime_set_autosuspend_delay(dev->dev, 5000);
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment