[PATCH i-g-t 23/23] tests/kms_ccs: Provide a hint as to what we're testing

[Ville Syrjala]

From: Ville Syrjälä <ville.syrjala at linux.intel.com>

Log the currently tested pixel format + modifier. Makes it
a bit easier to figure out what actually failed when it did.

TODO: would be nicer to also indicate if we actually test
      anything or just skip the whole thing, but that would
      require a bit of restructuring of the test...

Reviewed-by: Juha-Pekka Heikkila <juhapekka.heikkila at gmail.com>
Signed-off-by: Ville Syrjälä <ville.syrjala at linux.intel.com>
---
 tests/intel/kms_ccs.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/tests/intel/kms_ccs.c b/tests/intel/kms_ccs.c
index 6409ad605f0d..06f40e2c2175 100644
--- a/tests/intel/kms_ccs.c
+++ b/tests/intel/kms_ccs.c
@@ -913,6 +913,9 @@ static int test_ccs(data_t *data)
 	igt_crc_t crc, ref_crc;
 	enum test_fb_flags fb_flags = 0;
 
+	igt_info("Testing format " IGT_FORMAT_FMT " / modifier " IGT_MODIFIER_FMT "\n",
+		 IGT_FORMAT_ARGS(data->format), IGT_MODIFIER_ARGS(data->ccs_modifier));
+
 	if (data->flags & TEST_CRC) {
 		data->pipe_crc = igt_pipe_crc_new(data->drm_fd, data->pipe,
 						  IGT_PIPE_CRC_SOURCE_AUTO);
-- 
2.44.2