From: Alex Deucher <alexdeucher@gmail.com>
To: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
airlied@gmail.com, daniel.vetter@ffwll.ch
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: [pull] amdgpu drm-next-5.1
Date: Wed, 13 Mar 2019 14:42:49 -0500 [thread overview]
Message-ID: <20190313194249.3346-1-alexander.deucher@amd.com> (raw)
Hi Dave, Daniel,
A few fixes for 5.1:
- Update golden regs for gfx9
- Powerplay fixes
The following changes since commit 59d3191f14dc18881fec1172c7096b7863622803:
drm/amd/display: don't call dm_pp_ function from an fpu block (2019-03-06 15:31:20 -0500)
are available in the Git repository at:
git://people.freedesktop.org/~agd5f/linux drm-next-5.1
for you to fetch changes up to f7b1844bacecca96dd8d813675e4d8adec02cd66:
drm/amdgpu: Update gc golden setting for vega family (2019-03-11 15:57:20 -0500)
----------------------------------------------------------------
Evan Quan (2):
drm/amd/powerplay: set max fan target temperature as 105C
drm/amd/powerplay: correct power reading on fiji
shaoyunl (1):
drm/amdgpu: Update gc golden setting for vega family
drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 1 +
drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c | 6 +++---
.../drm/amd/powerplay/hwmgr/vega20_processpptables.c | 17 +++++++++++++++++
3 files changed, 21 insertions(+), 3 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-03-13 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 19:42 Alex Deucher [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-07 20:25 [pull] amdgpu drm-next-5.1 Alex Deucher
2019-02-08 21:02 Alex Deucher
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=20190313194249.3346-1-alexander.deucher@amd.com \
--to=alexdeucher@gmail.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--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;
as well as URLs for NNTP newsgroup(s).