All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: Pranay Samala <pranay.samala@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <karthik.b.s@intel.com>, <sameer.lattannavar@intel.com>
Subject: Re: [PATCH i-g-t] tests/kms_plane_alpha_blend: Reduce test complexity for simulation
Date: Mon, 21 Jul 2025 22:50:37 +0530	[thread overview]
Message-ID: <d9a94bb7-767b-403a-b89f-e3c4c2ce7e02@intel.com> (raw)
In-Reply-To: <20250719170838.1340070-1-pranay.samala@intel.com>

Hi Pranay,

On 19-07-2025 10:38 pm, Pranay Samala wrote:
> Reduce the number of plane alpha value iterations, and limit execution
> to a single plane for each pipe to enable this test on simulation.
>
> Signed-off-by: Pranay Samala <pranay.samala@intel.com>
> ---
>   tests/kms_plane_alpha_blend.c | 13 +++++++++++--
>   1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/tests/kms_plane_alpha_blend.c b/tests/kms_plane_alpha_blend.c
> index 047cc57b4..696bb1e5e 100644
> --- a/tests/kms_plane_alpha_blend.c
> +++ b/tests/kms_plane_alpha_blend.c
> @@ -79,6 +79,8 @@ typedef struct {
>   	igt_pipe_crc_t *pipe_crc;
>   } data_t;
>   
> +static bool in_simulation;
> +
>   static void __draw_gradient(struct igt_fb *fb, int w, int h, double a, cairo_t *cr)
>   {
>   	cairo_pattern_t *pat;
> @@ -289,7 +291,7 @@ static void basic_alpha(data_t *data, enum pipe pipe, igt_plane_t *plane)
>   {
>   	igt_display_t *display = &data->display;
>   	igt_crc_t ref_crc, crc;
> -	int i;
> +	int i, max_alpha_value;
>   
>   	/* Testcase 1: alpha = 0.0, plane should be transparent. */
>   	igt_display_commit2(display, COMMIT_ATOMIC);
> @@ -298,8 +300,10 @@ static void basic_alpha(data_t *data, enum pipe pipe, igt_plane_t *plane)
>   
>   	igt_plane_set_fb(plane, &data->argb_fb_0);
>   
> +	max_alpha_value = in_simulation ? 160 : 256;
> +
>   	/* transparent fb should be transparent, no matter what.. */
> -	for (i = 7; i < 256; i += 8) {
> +	for (i = 7; i < max_alpha_value; i += 8) {
>   		igt_plane_set_prop_value(plane, IGT_PLANE_ALPHA, i | (i << 8));
>   		igt_display_commit2(display, COMMIT_ATOMIC);
>   
> @@ -564,6 +568,9 @@ static void run_test_on_pipe_planes(data_t *data, enum pipe pipe, igt_output_t *
>   		igt_info("Testing plane %u\n", plane->index);
>   		test(data, pipe, plane);
>   		igt_plane_set_fb(plane, NULL);
> +
> +		if (in_simulation)
> +			break;
If we are breaking after first plane, how do we know if that plane 
supports alpha?
We need to have something like valid_plane which supports alpha and 
other constraints and then break.
That will imply, we have tested with atleast 1 plane supporting alpha 
and other constraints.
>   	}
>   
>   	igt_output_set_pipe(output, PIPE_NONE);
> @@ -743,6 +750,8 @@ igt_main_args("e", NULL, help_str, opt_handler, NULL)
>   		for_each_pipe(&data.display, pipe)
>   			active_pipes[last_pipe++] = pipe;
>   		last_pipe--;
> +
> +		in_simulation = igt_run_in_simulation();
>   	}
>   
>   	run_subtests(&data);


  parent reply	other threads:[~2025-07-21 17:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-19 17:08 [PATCH i-g-t] tests/kms_plane_alpha_blend: Reduce test complexity for simulation Pranay Samala
2025-07-19 17:56 ` ✗ Xe.CI.BAT: failure for " Patchwork
2025-07-19 18:04 ` ✓ i915.CI.BAT: success " Patchwork
2025-07-19 19:48 ` ✓ i915.CI.Full: " Patchwork
2025-07-21 14:33 ` ✗ Xe.CI.Full: failure " Patchwork
2025-07-21 17:20 ` Sharma, Swati2 [this message]
2025-07-28  3:54   ` [PATCH i-g-t] " Samala, Pranay
2025-07-29  7:53     ` Sharma, Swati2
2025-07-23  7:47 ` Kamil Konieczny
2025-07-28  3:51   ` Samala, Pranay
2025-07-29 14:15 ` ✓ i915.CI.BAT: success for tests/kms_plane_alpha_blend: Reduce test complexity for simulation (rev2) Patchwork
2025-07-29 14:50 ` ✓ Xe.CI.BAT: " Patchwork
2025-07-29 20:49 ` ✗ Xe.CI.Full: failure " Patchwork
2025-07-29 22:40 ` ✗ i915.CI.Full: " Patchwork
2025-07-30  9:33 ` ✓ i915.CI.Full: success " Patchwork

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=d9a94bb7-767b-403a-b89f-e3c4c2ce7e02@intel.com \
    --to=swati2.sharma@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=karthik.b.s@intel.com \
    --cc=pranay.samala@intel.com \
    --cc=sameer.lattannavar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.