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

[Juha-Pekka Heikkila]

Reviewed-by: Juha-Pekka Heikkila <juhapekka.heikkila at gmail.com>

On 3.7.2024 2.28, Ville Syrjala wrote:
> 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...
> 
> 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 8d3932de093e..3ed270a84c50 100644
> --- a/tests/intel/kms_ccs.c
> +++ b/tests/intel/kms_ccs.c
> @@ -944,6 +944,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);