summaryrefslogtreecommitdiffstats
path: root/Documentation/gpu
diff options
context:
space:
mode:
authorYogesh Mohan Marimuthu2019-05-17 12:16:58 +0200
committerAlex Deucher2019-05-24 19:46:38 +0200
commitf1e5e913028669c2bbac6664b8f01cb124349692 (patch)
tree2664362186d560d5ba8c988bde3446c227efd811 /Documentation/gpu
parentdrm/amd/display: Use new connector state when getting color depth (diff)
downloadkernel-qcow2-linux-f1e5e913028669c2bbac6664b8f01cb124349692.tar.gz
kernel-qcow2-linux-f1e5e913028669c2bbac6664b8f01cb124349692.tar.xz
kernel-qcow2-linux-f1e5e913028669c2bbac6664b8f01cb124349692.zip
drm/amdgpu: sort probed modes before adding common modes
[Why] There are monitors which can have more than one preferred mode set. There are chances in these monitors that if common modes are added in function amdgpu_dm_connector_add_common_modes(), these common modes can be calculated with different preferred mode than the one used in function decide_crtc_timing_for_drm_display_mode(). The preferred mode can be different because after common modes are added, the mode list is sorted and this changes the order of preferred modes in the list. The first mode in the list with preferred flag set is selected as preferred mode. Due to this the preferred mode selected varies. If same preferred mode is not selected in common mode calculation and crtc timing, then during mode set instead of setting preferred timing, common mode timing will be applied which can cause "out of range" message in the monitor with monitor blanking out. [How] Sort the modes before adding common modes. The same sorting function is called during common mode addition and deciding crtc timing. Signed-off-by: Yogesh Mohan Marimuthu <yogesh.mohanmarimuthu@amd.com> Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'Documentation/gpu')
0 files changed, 0 insertions, 0 deletions