diff options
| author | Lyude Paul <lyude@redhat.com> | 2020-04-03 16:03:25 -0400 |
|---|---|---|
| committer | Lyude Paul <lyude@redhat.com> | 2020-04-06 15:55:44 -0400 |
| commit | 61272e47c18cd05c0c5e5a4a2bee736bf37d765d (patch) | |
| tree | 511a3a1134ceb2cd9aab2d0b45b461cea095c141 /drivers/gpu/drm/drm_dp_mst_topology.c | |
| parent | cbfb1b74438fdab9ab34a24bb3a206033d807dc0 (diff) | |
| download | linux-61272e47c18cd05c0c5e5a4a2bee736bf37d765d.tar.bz2 | |
drm/dp_mst: Don't drop NAKs for down responses
It looks like that when we introduced the ability to handle multiple
down requests at once, we accidentally started dropping NAK replies -
causing sideband messages which got NAK'd to seemingly timeout and cause
all sorts of weirdness.
So, fix this by making sure we don't return from
drm_dp_mst_handle_down_rep() early, but instead treat NAKs like any
other message.
Signed-off-by: Lyude Paul <lyude@redhat.com>
Fixes: fbc821c4a506 ("drm/mst: Support simultaneous down replies")
Cc: Wayne Lin <Wayne.Lin@amd.com>
Cc: Wayne Lin <waynelin@amd.com>
Cc: Sean Paul <seanpaul@chromium.org>
Link: https://patchwork.freedesktop.org/patch/msgid/20200403200325.885628-1-lyude@redhat.com
Reviewed-by: Sean Paul <sean@poorly.run>
Diffstat (limited to 'drivers/gpu/drm/drm_dp_mst_topology.c')
| -rw-r--r-- | drivers/gpu/drm/drm_dp_mst_topology.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c b/drivers/gpu/drm/drm_dp_mst_topology.c index 6994076cbdc7..80067ea5c50e 100644 --- a/drivers/gpu/drm/drm_dp_mst_topology.c +++ b/drivers/gpu/drm/drm_dp_mst_topology.c @@ -3813,7 +3813,6 @@ static int drm_dp_mst_handle_down_rep(struct drm_dp_mst_topology_mgr *mgr) txmsg->reply.u.nak.reason, drm_dp_mst_nak_reason_str(txmsg->reply.u.nak.reason), txmsg->reply.u.nak.nak_data); - goto out_clear_reply; } memset(msg, 0, sizeof(struct drm_dp_sideband_msg_rx)); |