summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/amd/display/dc/inc/resource.h
diff options
context:
space:
mode:
authorWenjing Liu <wenjing.liu@amd.com>2022-08-31 15:22:56 -0400
committerAlex Deucher <alexander.deucher@amd.com>2022-09-19 15:12:16 -0400
commitcc67aae1e3a330e18ead512b525b8721a3b05a6c (patch)
treeecd9bd211f60e0e38e7672d9361295796abc08a9 /drivers/gpu/drm/amd/display/dc/inc/resource.h
parent9c75891feef0f9f67cf1c8f8038371006e25d23f (diff)
drm/amd/display: support proper mst payload removal when link is not in mst mode in dc
[why] When user unplugs mst hubs, the current code will forcefully zero entire mst payload allocation table structure stored in link before we deallocate actual payload when disabling stream. During the first disable stream sequence, we will use current mst payload allocation table to determine if link should be turned off. Because we zero out it before we are disabling stream, the payload allocation table stored in link doesn't represent the actual allocation status, so we turn off link at the first disable stream without waiting until all streams' payloads have been deallocated. This avoilates the designed deallocation sequence and caused system hang in DP2 scenario. [how] Remove payload during deallocation and never zero payload allocation structure without actually deallocating payload. Reviewed-by: Jun Lei <Jun.Lei@amd.com> Acked-by: Wayne Lin <wayne.lin@amd.com> Signed-off-by: Wenjing Liu <wenjing.liu@amd.com> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/display/dc/inc/resource.h')
0 files changed, 0 insertions, 0 deletions