Created attachment 145940 [details] dmesg on boot
LG Gram 13Z980, KBL hardware. On boot PSR is not enabled, but the debugfs shows it is supported by sink. After-suspend-resume PSR get activated
(In reply to s.zharkoff from comment #2) > LG Gram 13Z980, KBL hardware. On boot PSR is not enabled, but the debugfs > shows it is supported by sink. After-suspend-resume PSR get activated CC'ing Jose and Imre here.
5.4-rc7 is working OK. PSR1 enabled.
What version was you running? But looks like it is fixed in newer kernel, gonna close it okay? If it happens again please also try with drm-tip kernel and attach the logs again. Thanks
It is working in 5.4-rc7, but broken in drm-tip tree.
The log is from drm-tip?
If not can you attach it?
Yes, the log is from drm-tip. The dfference is that intel_psr_enable_locked is not called in drm-tip at the boot time baut called on resume, but on 5.4-rc7 it is called at the boot time. So with drm-tip the system detects that sink is psr1 compatible but somehow skips the activation step. In 5.4-rc7 main tree it activetes psr on initial boot. I tried to find out where it shoud be triggered but my knowledge is not enough for it. I've just tried to comment out all the points where the psr is deactivated due to errors and it is still not enabled after boot until first suspend-resume. So it is not activated and then disabled, it is just not activated.
I'm reproducing it too, working on a solution. Thanks
Hi Here is the fix: https://patchwork.freedesktop.org/series/70000/ Could you test it? Thanks
Tested drm-tip with the patch - work fine, psr activates at boot and continue working after resume from hibernation. So for me bug seems fixed.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/590.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.