From: Alex Deucher <alexander.deucher@amd.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-fixes-6.4
Date: Thu, 11 May 2023 10:17:55 -0400 [thread overview]
Message-ID: <20230511141755.7896-1-alexander.deucher@amd.com> (raw)
Hi Dave, Daniel,
Fixes for 6.4.
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
are available in the Git repository at:
https://gitlab.freedesktop.org/agd5f/linux.git tags/amd-drm-fixes-6.4-2023-05-11
for you to fetch changes up to 996e93a3fe74dcf9d467ae3020aea42cc3ff65e3:
drm/amdgpu: change gfx 11.0.4 external_id range (2023-05-11 09:11:14 -0400)
----------------------------------------------------------------
amdgpu:
- VCN3 fixes
- APUs always support PCI atomics
- Legacy power management fixes
- DCN 3.1.4 fix
- DCFCLK fix
- Fix several RAS irq refcount mismatches
- GPU Reset fix
- GFX 11.0.4 fix
----------------------------------------------------------------
Alvin Lee (1):
drm/amd/display: Enforce 60us prefetch for 200Mhz DCFCLK modes
Guchun Chen (4):
drm/amd/pm: parse pp_handle under appropriate conditions
drm/amdgpu: disable sdma ecc irq only when sdma RAS is enabled in suspend
drm/amd/pm: avoid potential UBSAN issue on legacy asics
drm/amdgpu/gfx: disable gfx9 cp_ecc_error_irq only when enabling legacy gfx ras
Horatio Zhang (1):
drm/amdgpu: drop gfx_v11_0_cp_ecc_error_irq_funcs
Leo Chen (1):
drm/amd/display: Add symclk workaround during disable link output
Lin.Cao (1):
drm/amdgpu: Fix vram recover doesn't work after whole GPU reset (v2)
Saleemkhan Jamadar (1):
drm/amdgpu/jpeg: Remove harvest checking for JPEG3
Thong Thai (1):
drm/amdgpu/nv: update VCN 3 max HEVC encoding resolution
Yifan Zhang (2):
drm/amdgpu: set gfx9 onwards APU atomics support to be true
drm/amdgpu: change gfx 11.0.4 external_id range
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 12 +++-
drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c | 8 ++-
drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c | 46 ---------------
drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 3 +-
drivers/gpu/drm/amd/amdgpu/jpeg_v3_0.c | 1 +
drivers/gpu/drm/amd/amdgpu/nv.c | 22 ++++++--
drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c | 8 ++-
drivers/gpu/drm/amd/amdgpu/soc21.c | 2 +-
.../gpu/drm/amd/display/dc/dcn314/dcn314_hwseq.c | 65 ++++++++++++++++++++++
.../gpu/drm/amd/display/dc/dcn314/dcn314_hwseq.h | 2 +
.../gpu/drm/amd/display/dc/dcn314/dcn314_init.c | 2 +-
.../amd/display/dc/dml/dcn32/display_mode_vba_32.c | 5 +-
.../amd/display/dc/dml/dcn32/display_mode_vba_32.h | 1 +
drivers/gpu/drm/amd/pm/amdgpu_dpm.c | 25 ++++++---
14 files changed, 131 insertions(+), 71 deletions(-)
next reply other threads:[~2023-05-11 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 14:17 Alex Deucher [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-23 21:18 [pull] amdgpu drm-fixes-6.4 Alex Deucher
2023-06-23 21:39 ` Dave Airlie
2023-06-23 23:44 ` Linus Torvalds
2023-06-01 3:38 Alex Deucher
2023-05-18 17:48 Alex Deucher
2023-05-04 3:40 Alex Deucher
2023-04-27 3:30 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=20230511141755.7896-1-alexander.deucher@amd.com \
--to=alexander.deucher@amd.com \
--cc=airlied@gmail.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