From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PULL] drm-fixes
Date: Sat, 1 Oct 2022 00:19:28 +0200 [thread overview]
Message-ID: <YzdrcM2YAK4qyePP@phenom.ffwll.local> (raw)
Hi Linus,
As Alex mentioned already, here's some last minute amd fixes that would be
nice to also include in the final release.
drm-fixes-2022-10-01:
amdgpu:
- VCN 4.x and GC 11.x fixes, mostly around fw
Cheers, Daniel
The following changes since commit 6643b3836f3908c4f77883b2fae72451e85cf3ca:
Merge tag 'drm-intel-fixes-2022-09-29' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes (2022-09-30 09:28:58 +1000)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2022-10-01
for you to fetch changes up to 414208e48963fdb136240d7f59c15e627832d288:
Merge tag 'amd-drm-fixes-6.0-2022-09-30-1' of https://gitlab.freedesktop.org/agd5f/linux into drm-fixes (2022-09-30 23:10:55 +0200)
----------------------------------------------------------------
amdgpu:
- VCN 4.x and GC 11.x fixes, mostly around fw
----------------------------------------------------------------
Daniel Vetter (1):
Merge tag 'amd-drm-fixes-6.0-2022-09-30-1' of https://gitlab.freedesktop.org/agd5f/linux into drm-fixes
Hawking Zhang (8):
drm/amdgpu: save rlcv/rlcp ucode version in amdgpu_gfx
drm/amdgpu: add helper to init rlc fw in header v2_0
drm/amdgpu: add helper to init rlc fw in header v2_1
drm/amdgpu: add helper to init rlc fw in header v2_2
drm/amdgpu: add helper to init rlc fw in header v2_3
drm/amdgpu: add helper to init rlc fw in header v2_4
drm/amdgpu: add helper to init rlc firmware
drm/amdgpu/gfx11: switch to amdgpu_gfx_rlc_init_microcode
Sonny Jiang (2):
drm/amdgpu: Enable VCN DPG for GC11_0_1
drm/amdgpu: Enable sram on vcn_4_0_2
drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.h | 4 +
drivers/gpu/drm/amd/amdgpu/amdgpu_rlc.c | 264 ++++++++++++++++++++++++++++++
drivers/gpu/drm/amd/amdgpu/amdgpu_rlc.h | 4 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_ucode.h | 4 +
drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c | 2 +-
drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c | 151 +----------------
drivers/gpu/drm/amd/amdgpu/soc21.c | 1 +
7 files changed, 281 insertions(+), 149 deletions(-)
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next reply other threads:[~2022-09-30 22:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 22:19 Daniel Vetter [this message]
2022-09-30 23:29 ` [PULL] drm-fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-12-06 21:12 Simona Vetter
2024-12-06 21:39 ` pr-tracker-bot
2023-01-06 23:05 Daniel Vetter
2023-01-06 23:58 ` pr-tracker-bot
2021-10-01 16:57 Daniel Vetter
2021-10-01 17:45 ` pr-tracker-bot
2021-04-16 13:32 Daniel Vetter
2021-04-16 15:15 ` pr-tracker-bot
2021-01-08 15:57 Daniel Vetter
2021-01-08 23:49 ` pr-tracker-bot
2020-03-06 21:08 Daniel Vetter
2020-03-06 22:20 ` pr-tracker-bot
2019-07-26 19:45 Daniel Vetter
2019-07-26 21:40 ` pr-tracker-bot
2019-01-11 23:06 Daniel Vetter
2019-01-12 18:45 ` pr-tracker-bot
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=YzdrcM2YAK4qyePP@phenom.ffwll.local \
--to=daniel.vetter@ffwll.ch \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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