summaryrefslogtreecommitdiffstats
path: root/certs
diff options
context:
space:
mode:
authorJun Lei <Jun.Lei@amd.com>2019-05-03 15:59:54 -0400
committerAlex Deucher <alexander.deucher@amd.com>2019-06-22 09:34:12 -0500
commit1621f4c417bf31e2b741a3d876b1d61435a41e18 (patch)
tree3c8c5a44c130e8e2f1d8c9f03988a4cad0bb2fe6 /certs
parent278141f58e2c9c8f7830f40086c1d43edc6c268b (diff)
downloadlinux-stable-1621f4c417bf31e2b741a3d876b1d61435a41e18.tar.gz
linux-stable-1621f4c417bf31e2b741a3d876b1d61435a41e18.tar.bz2
linux-stable-1621f4c417bf31e2b741a3d876b1d61435a41e18.zip
drm/amd/display: always use 4 dp lanes for dml
[why] current DML logic uses currently trained setting for number of dp lanes in DML calculations. this is obviously flawed since just because 1 lane is in use doesn't mean only 1 lane can be used this causes mode validation to fail depending on current state, which is incorrect [how] DML should always assume 4 lanes are available. validation of bandwidth is not supposed to be handled by DML, since we do link validation without DML already also, DML is expecting there to be a copy of the max state, this state is removed when update_bounding_box is called to update actual SKU clocks. fix this as well by duping last state. Signed-off-by: Jun Lei <Jun.Lei@amd.com> Reviewed-by: Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com> Acked-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Acked-by: Eric Yang <eric.yang2@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'certs')
0 files changed, 0 insertions, 0 deletions