Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Kahola, Mika" <mika.kahola@intel.com>
To: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_plane: fix pixel format (-clamping) tests
Date: Thu, 29 Oct 2020 12:43:06 +0000	[thread overview]
Message-ID: <c372276a30e84ce0a356eafc96e876d1@intel.com> (raw)
In-Reply-To: <20201026130811.11136-1-juhapekka.heikkila@gmail.com>

> -----Original Message-----
> From: igt-dev <igt-dev-bounces@lists.freedesktop.org> On Behalf Of Juha-
> Pekka Heikkila
> Sent: Monday, October 26, 2020 3:08 PM
> To: igt-dev@lists.freedesktop.org
> Subject: [igt-dev] [PATCH i-g-t] tests/kms_plane: fix pixel format (-clamping)
> tests
> 
> cdclk caused modesets mid test will mess up crc sequence where two
> consecutive frames will get same crc. If there come modeset restart round
> for given set as modeset will anyway happen only on first color.
> 
> Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> ---
>  tests/kms_plane.c | 28 ++++++++++++++++++++++------
>  1 file changed, 22 insertions(+), 6 deletions(-)
> 
> diff --git a/tests/kms_plane.c b/tests/kms_plane.c index
> e42c71cd9..4ce859fba 100644
> --- a/tests/kms_plane.c
> +++ b/tests/kms_plane.c
> @@ -560,9 +560,11 @@ static void capture_format_crcs(data_t *data, enum
> pipe pipe,
>  	struct drm_event_vblank ev;
>  	int i;
> 
> +restart_round:
>  	for (i = 0; i < data->num_colors; i++) {
>  		const color_t *c = &data->colors[i];
>  		struct igt_fb old_fb = *fb;
> +		int ret;
> 
>  		prepare_format_color(data, pipe, plane, format, modifier,
>  				     width, height, encoding, range, c, fb); @@
> -593,10 +595,22 @@ static void capture_format_crcs(data_t *data, enum
> pipe pipe,
>  			 * to be prepared in parallel while the current fb
>  			 * awaits to be latched.
>  			 */
> -			igt_display_commit_atomic(&data->display,
> -
> DRM_MODE_ATOMIC_ALLOW_MODESET |
> -
> DRM_MODE_ATOMIC_NONBLOCK |
> -
> DRM_MODE_PAGE_FLIP_EVENT, NULL);
> +			ret = igt_display_try_commit_atomic(&data->display,
> +
> DRM_MODE_ATOMIC_NONBLOCK |
> +
> DRM_MODE_PAGE_FLIP_EVENT, NULL);
> +			if (ret) {
> +				/*
> +				 * there was needed modeset for pixel
> format.
> +				 * modeset here happen only on first color of
> +				 * given set so restart round as modeset will
> +				 * mess up crc frame sequence.
> +				 */
> +				igt_display_commit_atomic(&data->display,
> +
> DRM_MODE_ATOMIC_ALLOW_MODESET,
> +							  NULL);
> +				igt_remove_fb(data->drm_fd, &old_fb);
> +				goto restart_round;
> +			}

I tried to figure out the patch and it seems that we need to do modeset only once, right? However, there is a theoretical chance (probability maybe next to nothing) that we keep looping on restart_found. Therefore, I was thinking that we should limit the restarts to 1 or to some finite number?

Cheers,
Mika
>  		} else {
>  			/*
>  			 * Last moment to grab the previous crc @@ -815,8
> +829,10 @@ static bool test_format_plane(data_t *data, enum pipe pipe,
> 
>  		igt_plane_set_fb(plane, &test_fb);
> 
> -		ret = igt_display_try_commit_atomic(&data->display,
> DRM_MODE_ATOMIC_TEST_ONLY, NULL);
> -
> +		ret = igt_display_try_commit_atomic(&data->display,
> +
> DRM_MODE_ATOMIC_TEST_ONLY |
> +
> DRM_MODE_ATOMIC_ALLOW_MODESET,
> +						    NULL);
>  		if (!ret) {
>  			width = test_fb.width;
>  			height = test_fb.height;
> --
> 2.28.0
> 
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2020-10-29 12:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 13:08 [igt-dev] [PATCH i-g-t] tests/kms_plane: fix pixel format (-clamping) tests Juha-Pekka Heikkila
2020-10-27 16:59 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2020-10-27 21:21 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-10-27 23:04 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-10-28  7:39   ` Juha-Pekka Heikkila
2020-10-28 16:46     ` Vudum, Lakshminarayana
2020-10-28 16:22 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
2020-10-29 12:43 ` Kahola, Mika [this message]
2020-10-29 18:23   ` [igt-dev] [PATCH i-g-t] " Juha-Pekka Heikkila
2020-10-30  9:07     ` Kahola, Mika
2020-10-30 13:40       ` Juha-Pekka Heikkila

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c372276a30e84ce0a356eafc96e876d1@intel.com \
    --to=mika.kahola@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=juhapekka.heikkila@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox