From: Alex Deucher <alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
daniel.vetter-/w4YWyX8dFk@public.gmane.org
Cc: Alex Deucher <alexander.deucher-5C7GfCeVMHo@public.gmane.org>
Subject: [pull] amdgpu, amdkfd drm-fixes-5.0
Date: Wed, 16 Jan 2019 17:45:24 -0500 [thread overview]
Message-ID: <20190116224524.3314-1-alexander.deucher@amd.com> (raw)
Hi Dave, Daniel,
Fixes for 5.0:
- Fix KFD on ARM64
- Fix KFD topology with mixed APU and dGPU systems
- Powerplay fix for vega12
- DC Raven fixes
- Freesync fix
The following changes since commit e2d3c414ec0f9d1557c8c5ff2c32166e68bbc4ad:
Merge tag 'drm-intel-fixes-2019-01-11' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes (2019-01-11 10:26:21 +0100)
are available in the Git repository at:
git://people.freedesktop.org/~agd5f/linux drm-fixes-5.0
for you to fetch changes up to 35dad45d5cad3c9ca8d6a338cbf668cd7ea86469:
drm/amd/display: Detach backlight from stream (2019-01-16 17:11:47 -0500)
----------------------------------------------------------------
Alex Deucher (1):
Revert "drm/amdgpu: validate user GEM object size"
Charlene Liu (1):
drm/amd/display: fix PME notification not working in RV desktop
David Francis (1):
drm/amd/display: Detach backlight from stream
Felix Kuehling (2):
drm/amdkfd: Allow building KFD on ARM64 (v2)
drm/amdkfd: Don't assign dGPUs to APU topology devices
Josip Pavic (1):
drm/amd/display: Pack DMCU iRAM alignment
Kenneth Feng (1):
drm/amd/powerplay: run acg btc for Vega12
Michel Dänzer (1):
Revert "drm/amdgpu: validate user pitch alignment"
Nicholas Kazlauskas (2):
drm/amd/display: Only get the connector state for VRR when toggled
drm/amd/display: Fix disabled cursor on top screen edge
Roman Li (1):
drm/amd/display: fix warning on raven hotplug
drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 18 ------------------
drivers/gpu/drm/amd/amdkfd/Kconfig | 4 ++--
drivers/gpu/drm/amd/amdkfd/kfd_crat.c | 8 ++++++++
drivers/gpu/drm/amd/amdkfd/kfd_topology.c | 21 ++++++++++++++-------
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 4 ++--
drivers/gpu/drm/amd/display/dc/core/dc_link.c | 12 +-----------
drivers/gpu/drm/amd/display/dc/dc_link.h | 3 +--
drivers/gpu/drm/amd/display/dc/dc_stream.h | 1 -
.../drm/amd/display/dc/dce110/dce110_hw_sequencer.c | 7 ++++++-
drivers/gpu/drm/amd/display/dc/dcn10/dcn10_dpp.c | 2 +-
drivers/gpu/drm/amd/display/dc/dcn10/dcn10_hubp.c | 2 +-
.../drm/amd/display/dc/dcn10/dcn10_hw_sequencer.c | 19 ++++++-------------
.../drm/amd/display/modules/power/power_helpers.c | 2 ++
drivers/gpu/drm/amd/powerplay/hwmgr/vega12_hwmgr.c | 21 +++++++++++++++++++++
14 files changed, 65 insertions(+), 59 deletions(-)
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
reply other threads:[~2019-01-16 22:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190116224524.3314-1-alexander.deucher@amd.com \
--to=alexdeucher-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=alexander.deucher-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=daniel.vetter-/w4YWyX8dFk@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.