summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_ucode.c
diff options
context:
space:
mode:
authorhersen wu <hersenxs.wu@amd.com>2022-11-14 14:29:56 -0500
committerAlex Deucher <alexander.deucher@amd.com>2023-01-17 15:41:19 -0500
commitaa9fdd5d5add50305d2022fa072fe6f189283415 (patch)
treed154e0fe3923d14ded3ff99333bde94a8840c1ed /drivers/gpu/drm/amd/amdgpu/amdgpu_ucode.c
parente36193123f3f5e4ac837f32daa78125d8e9d749b (diff)
downloadlinux-aa9fdd5d5add50305d2022fa072fe6f189283415.tar.gz
linux-aa9fdd5d5add50305d2022fa072fe6f189283415.tar.bz2
linux-aa9fdd5d5add50305d2022fa072fe6f189283415.zip
drm/amd/display: phase2 enable mst hdcp multiple displays
[why] For MST topology with 1 physical link and multiple connectors (>=2), e.g. daisy cahined MST + SST, or 1-to-multi MST hub, if userspace set to enable the HDCP simultaneously on all connected outputs, the commit tail iteratively call the hdcp_update_display() for each display (connector). However, the hdcp workqueue data structure for each link has only one DM connector and encryption status members, which means the work queue of property_validate/update() would only be triggered for the last connector within this physical link, and therefore the HDCP property value of other connectors would stay on DESIRED instead of switching to ENABLED, which is NOT as expected. [how] Use array of AMDGPU_DM_MAX_DISPLAY_INDEX for both aconnector and encryption status in hdcp workqueue data structure for each physical link. For property validate/update work queue, we iterates over the array and do similar operation/check for each connected display. Tested-by: Daniel Wheeler <Daniel.Wheeler@amd.com> Signed-off-by: hersen wu <hersenxs.wu@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_ucode.c')
0 files changed, 0 insertions, 0 deletions