Comment # 4
on bug 103277
from Jerry.Zuo@amd.com
(In reply to dwagner from comment #3) > (In reply to Jordan L from comment #2) > > Thanks, we can reproduce this too, should have something shortly. > > Any news on this? > > I am asking, because the current head of > https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next (as of > commit d66bebab317cc56a2a6d2438fcd89870c3d172ca) still has this very bug - > and that is even though within "git log" I can see in commit > 26c860d5579684528114c3875ef88f7796330eb5 there was > > Revert "drm/amd/display: Match actual state during S3 resume." > so I currently know of no way to make the current amd-staging-drm-next > resume from S3 sleep. S3 starts working since commit 95539e2be57. Test is performed on the following condition: Commit: c6f284d9888 Asic: Baffin 4K display: Acer H277HK S3 passed in 10 runs Please verify at your side as well. Thanks.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
