| Bug ID | 106363 |
|---|---|
| Summary | Powerplay support for SI asics |
| Product | DRI |
| Version | unspecified |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | enhancement |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | lemaitre.dulotus@yahoo.fr |
This is a feature request for powerplay support on SI asics. I can understand that they are not a priority but since they are (experimentally) supported by AMDgpu, I think they should have it.
Im on Tahiti and I just append amdgpu.dpm=3D1 to my kernel con= fig and things started working. DPMS, Suspend to Disk all is working fine.
(In reply to Gregor M=C3=BCnch from comment #1) > DPMS, Suspend to Disk all is working fine. Neither DPMS nor suspend to disk has anything to do with PowerPlay (or DPM) though. :)
dpm is enabled by default on SI parts so setting dpm=3D1 doesn= 't change anything.
(In reply to Alex Deucher from comment #3) > dpm is enabled by default on SI parts so setting= dpm=3D1 doesn't change > anything. This depends if you use amdgpu instead of radeon on SI. In that case amdgpu= .dpm seems to be disabled. I tried to enable DPMS and read through a bunch of tutorials configuring Xo= rg but nothing did work. Then I stumbled about a newsentry on phoronix mentioned this patch: https://lists.freedesktop.org/archives/amd-gfx/2018-May/022771.html There you change the behavior for CIK parts to use PP by default. The logic= of this patch changes amdgpu.dpm=3D-1 (auto) to switch from whatever to Powerp= lay. I started my Kernel with amdgpu.dpm=3D1 and everything suddenly worked like magic. Since I dont what Powerplay actually does in the Linux world and a quick go= ogle search came up with nothing and modinfo amdgpu just reveils dpm:DPM support (1 =3D enable, 0 =3D disable, -1 =3D auto) (int) but nothing about Powerplay I was really under the impression that DPM also enables Powerplay. Im sorry for the confusion.
(In reply to Gregor M=C3=BCnch from comment #4) > (In reply to Alex Deucher from comment #3) > > dpm is enabled by default on SI parts so setting dpm=3D1 doesn't = change > > anything. >=20 > This depends if you use amdgpu instead of radeon on SI. In that case > amdgpu.dpm seems to be disabled. nope. dpm is enabled by default on both radeon and amdgpu. > I tried to enable DPMS and read through a bunch = of tutorials configuring > Xorg but nothing did work. DPMS is not related to dpm at all. > Then I stumbled about a newsentry on phoronix me= ntioned this patch: > https://lists.freedesktop.org/archives/amd-gfx/2018-May/022771.ht= ml > There you change the behavior for CIK parts to use PP by default. The = logic > of this patch changes amdgpu.dpm=3D-1 (auto) to switch from whatever to > Powerplay. This change applies to CIK only not SI. >=20 >=20 > I started my Kernel with amdgpu.dpm=3D1 and everything suddenly worked= like > magic. >=20 > Since I dont what Powerplay actually does in the Linux world and a qui= ck > google search came up with nothing and modinfo amdgpu just reveils > dpm:DPM support (1 =3D enable, 0 =3D disable, -1 =3D auto) (int) > but nothing about Powerplay I was really under the impression that DPM= also > enables Powerplay. > Im sorry for the confusion. dpm and powerplay are just two sw implementations of the same hardware functionality. CIK and VI share the same SMU IP so they can share most of = the power code. SI uses an old SMU block and can't share the code so it still = uses the dpm implementation originally ported from radeon.
Thanks for your explanations Alex. Maybe useful for other: It turned out that Steam client has probably a bug preventing screensaver getting active. ht= tps://github.com/ValveSoftware/steam-for-linux/issues/5532 One more problem seems to be that Deepin or whatever still cant run the screensaver even after Steam was closed. http= s://github.com/linuxdeepin/developer-center/issues/567 Im sorry again for occupying this bug report.
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- 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/amd/issues/371.