linux

iv/linux

History

Nicholas Kazlauskas ec6e491353 drm/amd/display: Calculate bpc based on max_requested_bpc

[Why]
The only place where state->max_bpc is updated on the connector is
at the start of atomic check during drm_atomic_connector_check. It
isn't updated when adding the connectors to the atomic state after
the fact. It also doesn't necessarily reflect the right value when
called in amdgpu during mode validation outside of atomic check.

This can cause the wrong bpc to be used even if the max_requested_bpc
is the correct value.

[How]
Don't rely on state->max_bpc reflecting the real bpc value and just
do the min(...) based on display info bpc and max_requested_bpc.

Fixes: 01933ba42d3d ("drm/amd/display: Use current connector state if NULL when checking bpc")
Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Reviewed-by: Leo Li <sunpeng.li@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

2019-08-21 17:33:32 -05:00

amdgpu_dm_color.c

drm/amd/display: Rework CRTC color management

2019-06-22 09:34:13 -05:00

amdgpu_dm_crc.c

drm/amd: drop use of drmP.h in amdgpu.h

2019-06-10 22:59:53 +02:00

amdgpu_dm_debugfs.c

Merge branch 'drm-next' into drm-next-5.3

2019-06-25 08:42:25 -05:00

amdgpu_dm_debugfs.h

amdgpu_dm: no need to check return value of debugfs_create functions