[igt-dev] [v3 4/4] tests/kms_color: skip deep-color test for mst

[Swati Sharma]

In intel driver, for MST streams pipe_bpp is restricted to 8bpc.
So, deep-color >= 10bpc will never work for DP-MST even if panel
supports 10bpc.

Test checks panel supports 10bpc and tries to find such a
combination of mode that can really work with 10bpc. So, with
n1 modes in MST1 and n2 modes in MST2, test will try n1xn2 times
and eventually SKIP. However, trying with these many combinations
it is leading to excessive logging ultimately killing the test.

Once KMD FIXME, is resolved this MST constraint can be removed.

v2: -moved check (Bhanu)

Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/8615
Signed-off-by: Swati Sharma <swati2.sharma at intel.com>
Reviewed-by: Bhanuprakash Modem <bhanuprakash.modem at intel.com>
---
 tests/kms_color.c | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/tests/kms_color.c b/tests/kms_color.c
index dded24c03..0b6e1d6f0 100644
--- a/tests/kms_color.c
+++ b/tests/kms_color.c
@@ -918,6 +918,15 @@ run_deep_color_tests_for_pipe(data_t *data, enum pipe p)
 
 		if (!panel_supports_deep_color(data->drm_fd, output->name))
 			continue;
+		/*
+		 * In intel driver, for MST streams pipe_bpp is
+		 * restricted to 8bpc. So, deep-color >= 10bpc
+		 * will never work for DP-MST even if the panel
+		 * supports 10bpc. Once KMD FIXME, is resolved
+		 * this MST constraint can be removed.
+		 */
+		if (is_intel_device(data->drm_fd) && igt_check_output_is_dp_mst(output))
+			continue;
 
 		igt_display_reset(&data->display);
 		igt_output_set_prop_value(output, IGT_CONNECTOR_MAX_BPC, 10);
-- 
2.25.1