All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lyude Paul <lyude@redhat.com>
To: amd-gfx@lists.freedesktop.org
Subject: [PATCH v2 0/4] drm/amdgpu: Regression fixes from MST atomic-only conversion
Date: Mon, 14 Nov 2022 17:17:51 -0500	[thread overview]
Message-ID: <20221114221754.385090-1-lyude@redhat.com> (raw)

There was a bit of unexpected fallout from the atomic-only conversion
patches that I had pushed a while ago, which mostly affected amdgpu.
This fixes most of the severe issues, although we're still investigating
some lingering issues (which I suspect may just fix themselves following
this patchset, but we'll see!).

This is -technically- a v2 as it's a continuation on this previous
series:

https://patchwork.freedesktop.org/series/110556/

and there were some rather important changes made since then that Wayne
pointed out, which may or may not fix the last few issues left on this
issue:

https://gitlab.freedesktop.org/drm/amd/-/issues/2171

Note I've omitted one KASAN fix, but that's because it was just getting
in the way of turning on KASAN and was definitely unrelated to this bug.
Will submit that one on it's own shortly.

Lyude Paul (4):
  drm/amdgpu/mst: Stop ignoring error codes and deadlocking
  drm/display/dp_mst: Fix drm_dp_mst_add_affected_dsc_crtcs() return
    code
  drm/amdgpu/dm/mst: Use the correct topology mgr pointer in
    amdgpu_dm_connector
  drm/amdgpu/dm/dp_mst: Don't grab mst_mgr->lock when computing DSC
    state

 .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c |  18 +-
 .../display/amdgpu_dm/amdgpu_dm_mst_types.c   | 254 ++++++++++--------
 .../display/amdgpu_dm/amdgpu_dm_mst_types.h   |  12 +-
 drivers/gpu/drm/display/drm_dp_mst_topology.c |   2 +-
 4 files changed, 155 insertions(+), 131 deletions(-)

-- 
2.37.3


             reply	other threads:[~2022-11-14 22:18 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 22:17 Lyude Paul [this message]
2022-11-14 22:17 ` [PATCH v2 1/4] drm/amdgpu/mst: Stop ignoring error codes and deadlocking Lyude Paul
2022-11-14 22:17   ` Lyude Paul
2022-11-14 22:17   ` Lyude Paul
2022-11-16  4:39   ` Lin, Wayne
2022-11-16  4:39     ` Lin, Wayne
2022-11-16  4:39     ` Lin, Wayne
2022-11-16 22:43     ` Lyude Paul
2022-11-16 22:43       ` Lyude Paul
2022-11-16 22:43       ` Lyude Paul
2022-11-18 19:17     ` Lyude Paul
2022-11-18 19:17       ` Lyude Paul
2022-11-18 19:17       ` Lyude Paul
2022-11-18 19:46       ` Alex Deucher
2022-11-18 19:46         ` Alex Deucher
2022-11-18 19:46         ` Alex Deucher
2022-11-18 19:47         ` Lyude Paul
2022-11-18 19:47           ` Lyude Paul
2022-11-18 19:47           ` Lyude Paul
2022-11-18 19:53           ` Lyude Paul
2022-11-18 19:53             ` Lyude Paul
2022-11-18 19:53             ` Lyude Paul
2022-11-18 20:06             ` Alex Deucher
2022-11-18 20:06               ` Alex Deucher
2022-11-18 20:06               ` Alex Deucher
2022-11-18 19:25   ` [PATCH v3] " Lyude Paul
2022-11-18 19:25     ` Lyude Paul
2022-11-18 19:25     ` Lyude Paul
2022-11-18 19:54     ` [v3] " Limonciello, Mario
2022-11-18 19:54       ` Limonciello, Mario
2022-11-18 19:54       ` Limonciello, Mario
2022-11-18 19:56       ` Lyude Paul
2022-11-18 19:56         ` Lyude Paul
2022-11-18 19:56         ` Lyude Paul
2022-11-14 22:17 ` [PATCH v2 2/4] drm/display/dp_mst: Fix drm_dp_mst_add_affected_dsc_crtcs() return code Lyude Paul
2022-11-14 22:17   ` Lyude Paul
2022-11-14 22:17   ` Lyude Paul
2022-11-14 22:17 ` [PATCH v2 3/4] drm/amdgpu/dm/mst: Use the correct topology mgr pointer in amdgpu_dm_connector Lyude Paul
2022-11-14 22:17   ` Lyude Paul
2022-11-14 22:17   ` Lyude Paul
2022-11-14 22:17 ` [PATCH v2 4/4] drm/amdgpu/dm/dp_mst: Don't grab mst_mgr->lock when computing DSC state Lyude Paul
2022-11-14 22:17   ` Lyude Paul
2022-11-14 22:17   ` Lyude Paul

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=20221114221754.385090-1-lyude@redhat.com \
    --to=lyude@redhat.com \
    --cc=amd-gfx@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.