All of lore.kernel.org
 help / color / mirror / Atom feed
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.6
Date: Wed, 11 Oct 2023 22:56:36 -0400	[thread overview]
Message-ID: <20231012025637.7783-1-alexander.deucher@amd.com> (raw)

Hi Dave, Daniel,

Fixes for 6.6.

The following changes since commit 94f6f0550c625fab1f373bb86a6669b45e9748b3:

  Linux 6.6-rc5 (2023-10-08 13:49:43 -0700)

are available in the Git repository at:

  https://gitlab.freedesktop.org/agd5f/linux.git tags/amd-drm-fixes-6.6-2023-10-11

for you to fetch changes up to 3806a8c64794661b15ff5ed28180ff9a5f79fce8:

  drm/amdgpu: fix SI failure due to doorbells allocation (2023-10-09 17:59:29 -0400)

----------------------------------------------------------------
amd-drm-fixes-6.6-2023-10-11:

amdgpu:
- Seemless boot fix
- Fix TTM BO resource check
- SI fix for doorbell handling

----------------------------------------------------------------
Christian König (1):
      drm/amdgpu: add missing NULL check

Daniel Miess (1):
      drm/amd/display: Don't set dpms_off for seamless boot

Icenowy Zheng (1):
      drm/amdgpu: fix SI failure due to doorbells allocation

 drivers/gpu/drm/amd/amdgpu/amdgpu_doorbell_mgr.c | 4 ++++
 drivers/gpu/drm/amd/amdgpu/amdgpu_object.h       | 2 +-
 drivers/gpu/drm/amd/display/dc/core/dc.c         | 3 +++
 3 files changed, 8 insertions(+), 1 deletion(-)

             reply	other threads:[~2023-10-12  2:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12  2:56 Alex Deucher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-26  3:54 [pull] amdgpu drm-fixes-6.6 Alex Deucher
2023-10-20  1:24 Alex Deucher
2023-10-05  3:43 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=20231012025637.7783-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 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.