Su Sung Chung 88147df030 drm/amd/display: fix calculation of total_data_read_bandwidth ... [why] by adding fast_validate flag, we are skipping some portion of dcn_validate_bandwidth code that is not necessary for mode validation. However we have a bug where it does not calculate v->total_data_read_bandwidth, which is one of the factors determines the result of the validation, and therefore report false positive during mode validation. [how] add calculation of v->total_data_read_bandwidth outside of the region that is guarded by fast_validate flag Signed-off-by: Su Sung Chung <Su.Chung@amd.com> Reviewed-by: Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com> Acked-by: Leo Li <sunpeng.li@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>		2019-05-31 10:39:31 -05:00
..
amdgpu_dm	drm/amd/display: Ensure DRR triggers in BP	2019-05-31 10:39:30 -05:00
dc	drm/amd/display: fix calculation of total_data_read_bandwidth	2019-05-31 10:39:31 -05:00
include	drm/amd/display: make clk mgr soc specific	2019-05-31 10:39:29 -05:00
modules	drm/amd/display: Don't use ROM for output TF if GAMMA_CS_TFM_1D	2019-05-31 10:39:29 -05:00
Kconfig	Merge branch 'drm-next-5.3' of git://people.freedesktop.org/~agd5f/linux into drm-next	2019-05-31 10:04:39 +10:00
Makefile	drm/amd/display: move clk_mgr files to right place	2019-05-31 10:39:31 -05:00
TODO	drm/amd/display: Convert remaining loggers off dc_logger	2018-07-13 14:48:42 -05:00