Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Shankar, Uma" <uma.shankar@intel.com>
To: "Joshi, Kunal1" <kunal1.joshi@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Latvala, Petri" <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_color_chamelium: time optimization
Date: Thu, 3 Dec 2020 12:13:33 +0000	[thread overview]
Message-ID: <e0bf4545ff7f4678830cf6cef7ae40a7@intel.com> (raw)
In-Reply-To: <20201110050334.2747067-1-kunal1.joshi@intel.com>



> -----Original Message-----
> From: Joshi, Kunal1 <kunal1.joshi@intel.com>
> Sent: Tuesday, November 10, 2020 10:34 AM
> To: igt-dev@lists.freedesktop.org
> Cc: Latvala, Petri <petri.latvala@intel.com>; Shankar, Uma
> <uma.shankar@intel.com>; B S, Karthik <karthik.b.s@intel.com>; Joshi, Kunal1
> <kunal1.joshi@intel.com>
> Subject: [PATCH i-g-t] tests/kms_color_chamelium: time optimization
> 
> Instead of going through all the delta even if we got success with one, now
> breaking when we pass, thus saving some time and decreasing load on
> chamelium for capturing the rest of the frames.

Looks Good to me.
Reviewed-by: Uma Shankar <uma.shankar@intel.com>

> Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com>
> ---
>  tests/kms_color_chamelium.c | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/tests/kms_color_chamelium.c b/tests/kms_color_chamelium.c index
> 310c021a..43bbe1f2 100644
> --- a/tests/kms_color_chamelium.c
> +++ b/tests/kms_color_chamelium.c
> @@ -610,9 +610,9 @@ run_tests_for_pipe(data_t *data, enum pipe p)
>  				expected_colors[1].g =
>  				expected_colors[2].b =
>  				0.25 + delta * (i - 2);
> -			success |= test_pipe_ctm(data, primary,
> -						 red_green_blue,
> -						 expected_colors, ctm);
> +			if(test_pipe_ctm(data, primary, red_green_blue,
> +					 expected_colors, ctm))
> +				break;
>  		}
>  		igt_assert(success);
>  	}
> @@ -632,9 +632,9 @@ run_tests_for_pipe(data_t *data, enum pipe p)
>  				expected_colors[1].g =
>  				expected_colors[2].b =
>  				0.5 + delta * (i - 2);
> -			success |= test_pipe_ctm(data, primary,
> -						 red_green_blue,
> -						 expected_colors, ctm);
> +			if(test_pipe_ctm(data, primary, red_green_blue,
> +					 expected_colors, ctm))
> +				break;
>  		}
>  		igt_assert(success);
>  	}
> @@ -654,9 +654,9 @@ run_tests_for_pipe(data_t *data, enum pipe p)
>  				expected_colors[1].g =
>  				expected_colors[2].b =
>  				0.75 + delta * (i - 3);
> -			success |= test_pipe_ctm(data, primary,
> -						 red_green_blue,
> -						 expected_colors, ctm);
> +			if(test_pipe_ctm(data, primary, red_green_blue,
> +					 expected_colors, ctm))
> +				break;
>  		}
>  		igt_assert(success);
>  	}
> --
> 2.25.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      parent reply	other threads:[~2020-12-03 12:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10  5:03 [igt-dev] [PATCH i-g-t] tests/kms_color_chamelium: time optimization Kunal Joshi
2020-11-10 12:26 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-11-10 13:50 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-12-03 12:13 ` Shankar, Uma [this message]

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=e0bf4545ff7f4678830cf6cef7ae40a7@intel.com \
    --to=uma.shankar@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kunal1.joshi@intel.com \
    --cc=petri.latvala@intel.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