Page MenuHomeFreeBSD

amdsmu: Diagnose S0i3 entry after resume
ClosedPublic

Authored by obiwac on Mon, Sep 14, 6:31 PM.
Tags
None
Referenced Files
F174624164: D59673.id186706.diff
Sun, Oct 4, 6:30 PM
Unknown Object (File)
Sat, Oct 3, 12:32 PM
Unknown Object (File)
Fri, Oct 2, 1:34 AM
Unknown Object (File)
Thu, Oct 1, 2:30 PM
Unknown Object (File)
Thu, Oct 1, 6:04 AM
Unknown Object (File)
Thu, Oct 1, 5:55 AM
Unknown Object (File)
Thu, Oct 1, 5:49 AM
Unknown Object (File)
Thu, Oct 1, 4:53 AM
Subscribers

Details

Summary

Print out diagnostic information after resuming from suspend-to-idle if
we failed to enter S0i3, i.e. the IP blocks that were blocking entry to
S0i3.

Don't give detailed IP block info for other SMUs than for Phoenix, as I
have not had a chance to test these yet and the SMU seems to be very
quirky.

Sponsored by: The FreeBSD Foundation

Test Plan

Purposely prevent S0i3 entry by e.g. not loading thunderbolt(4) or amdgpu and see if amdsmu(4) correctly reports the equivalent IP blocks after resuming from suspend-to-idle.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

only give IP block detail for Phoenix

IP block can have active time but not be blocking, actually

rebase & use new power_resume_check eventhandler

This revision is now accepted and ready to land.Fri, Sep 18, 7:34 AM
This revision was automatically updated to reflect the committed changes.