dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106363] Powerplay support for SI asics
Date: Wed, 20 Jun 2018 14:17:42 +0000	[thread overview]
Message-ID: <bug-106363-502-c4d5PEY2HI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106363-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1781 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106363

--- Comment #5 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Gregor Münch from comment #4)
> (In reply to Alex Deucher from comment #3)
> > dpm is enabled by default on SI parts so setting dpm=1 doesn't change
> > anything.
> 
> 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 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=-1 (auto) to switch from whatever to
> Powerplay.

This change applies to CIK only not SI.

> 
> 
> I started my Kernel with amdgpu.dpm=1 and everything suddenly worked like
> magic.
> 
> Since I dont what Powerplay actually does in the Linux world and a quick
> google search came up with nothing and modinfo amdgpu just reveils
> dpm:DPM support (1 = enable, 0 = disable, -1 = 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2880 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-06-20 14:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 20:47 [Bug 106363] Powerplay support for SI asics bugzilla-daemon
2018-06-19 14:26 ` bugzilla-daemon
2018-06-19 14:30 ` bugzilla-daemon
2018-06-19 14:42 ` bugzilla-daemon
2018-06-20  9:31 ` bugzilla-daemon
2018-06-20 14:17 ` bugzilla-daemon [this message]
2018-06-23 11:30 ` bugzilla-daemon
2019-11-19  8:37 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-106363-502-c4d5PEY2HI@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox