diff options
| author | Wayne Lin <Wayne.Lin@amd.com> | 2024-10-25 12:27:26 +0800 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2024-11-04 11:39:19 -0500 |
| commit | bc068194f548ef1f230d96c4398046bf59165992 (patch) | |
| tree | 2818924038b30c753535ed57f8376fc7820c3bd5 /drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | |
| parent | caccee7b296b1f6c37f09b5d4808606c66438e9d (diff) | |
| download | linux-bc068194f548ef1f230d96c4398046bf59165992.tar.gz linux-bc068194f548ef1f230d96c4398046bf59165992.tar.bz2 linux-bc068194f548ef1f230d96c4398046bf59165992.zip | |
drm/amd/display: Don't write DP_MSTM_CTRL after LT
[Why]
Observe after suspend/resme, we can't light up mst monitors under specific
mst hub. The reason is that driver still writes DPCD DP_MSTM_CTRL after LT.
It's forbidden even we write the same value for that dpcd register.
[How]
We already resume the mst branch device dpcd settings during
resume_mst_branch_status(). Leverage drm_dp_mst_topology_queue_probe() to
only probe the topology, not calling drm_dp_mst_topology_mgr_resume() which
will set DP_MSTM_CTRL as well.
Reviewed-by: Jerry Zuo <jerry.zuo@amd.com>
Signed-off-by: Wayne Lin <Wayne.Lin@amd.com>
Signed-off-by: Zaeem Mohamed <zaeem.mohamed@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/amdgpu/amdgpu_device.c')
0 files changed, 0 insertions, 0 deletions