All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Swati Sharma <swati2.sharma@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [v3 5/9] tests/kms_plane_scaling: Upscaling on 2 planes
Date: Wed, 9 Feb 2022 10:36:38 +0200	[thread overview]
Message-ID: <YgN9FpynUEiywoeL@intel.com> (raw)
In-Reply-To: <20220208055039.31306-6-swati2.sharma@intel.com>

On Tue, Feb 08, 2022 at 11:20:35AM +0530, Swati Sharma wrote:
> i915 driver supports 2 scalers per pipe. Added test case
> to upscale 2 overlay planes simultaneously on single pipe.
> 
> v2: -add check for min 2 scalers
>     -add igt_require() for overlay planes, fixes CRASH on KBL
> 
> v3: -test modified for n planes (Ville)
> 
> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
> ---
>  tests/kms_plane_scaling.c | 74 +++++++++++++++++++++++++++++++++++++++
>  1 file changed, 74 insertions(+)
> 
> diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
> index 22563fac..f813c5b4 100644
> --- a/tests/kms_plane_scaling.c
> +++ b/tests/kms_plane_scaling.c
> @@ -29,6 +29,11 @@
>  
>  IGT_TEST_DESCRIPTION("Test display plane scaling");
>  
> +/* Test flags. */
> +enum {
> +        TEST_UP_UP_SCALING = 1 << 0,
> +};
> +
>  typedef struct {
>  	uint32_t devid;
>  	int drm_fd;
> @@ -358,6 +363,67 @@ test_plane_downscaling(data_t *d, enum pipe pipe, igt_output_t *output)
>  	}
>  }
>  
> +static void
> +__test_plane_up_up_scaling(data_t *d, enum pipe pipe, igt_output_t *output)
> +{
> +	drmModeModeInfo *mode;
> +	int width, height;
> +	igt_display_t *display = &d->display;
> +
> +	cleanup_crtc(d);
> +
> +	igt_output_set_pipe(output, pipe);
> +	mode = igt_output_get_mode(output);
> +	width = height = 20;
> +
> +	for (int k = 0; k < display->pipes[pipe].n_planes; k++) {
> +		igt_plane_t *plane1, *plane2;
> +
> +		plane1 = &display->pipes[pipe].planes[k];
> +		igt_require(plane1);
> +		plane2 = &display->pipes[pipe].planes[k+1];
> +		igt_require(plane2);
> +
> +		if (plane1->type == DRM_PLANE_TYPE_PRIMARY  || plane1->type == DRM_PLANE_TYPE_CURSOR ||
> +		    plane2->type == DRM_PLANE_TYPE_PRIMARY || plane2->type ==DRM_PLANE_TYPE_CURSOR)
> +				continue;
> +
> +		igt_create_color_pattern_fb(display->drm_fd,
> +					    width, height,
> +					    DRM_FORMAT_XRGB8888,
> +					    I915_TILING_NONE,
> +					    1.0, 0.0, 0.0, &d->fb[1]);
> +		igt_create_color_pattern_fb(display->drm_fd,
> +					    width, height,
> +					    DRM_FORMAT_XRGB8888,
> +					    I915_TILING_NONE,
> +					    0.0, 1.0, 0.0, &d->fb[2]);

Recreating the same fbs every iteration seems pointless/expensive.

> +
> +		igt_plane_set_fb(plane1, &d->fb[1]);
> +		igt_plane_set_fb(plane2, &d->fb[2]);
> +
> +		/* 1st overlay plane upscaling */
> +		igt_plane_set_size(plane1, mode->hdisplay, mode->vdisplay);
> +		/* 2nd overlay plane upscaling */
> +		igt_plane_set_size(plane2, mode->hdisplay - 20, mode->vdisplay - 20);
> +		igt_display_commit2(display, COMMIT_ATOMIC);
> +
> +		igt_plane_set_fb(plane1, NULL);
> +		igt_plane_set_fb(plane2, NULL);
> +		igt_remove_fb(display->drm_fd, &d->fb[1]);
> +		igt_remove_fb(display->drm_fd, &d->fb[2]);
> +	}
> +}
> +
> +static void
> +test_plane_scaling_combo(data_t *d, enum pipe pipe, igt_output_t *output, uint32_t flags)
> +{
> +	igt_require(get_num_scalers(d, pipe) >= 2);
> +
> +	if (flags & TEST_UP_UP_SCALING)

What's the point of this flag based dispatcher thing? Just call the
right function directly?

> +		__test_plane_up_up_scaling(d, pipe, output);
> +}
> +
>  static bool test_pipe_iteration(data_t *data, enum pipe pipe, int iteration)
>  {
>  	if (!is_i915_device(data->drm_fd) ||
> @@ -689,6 +755,14 @@ igt_main_args("", long_opts, help_str, opt_handler, &data)
>  					test_plane_downscaling(&data, pipe, output);
>  		}
>  
> +		igt_describe("Tests upscaling of 2 overlay planes.");
> +		igt_subtest_with_dynamic("plane-up-up-scaling") {

Bit of a funny name that, but don't really have a great idea
how to make it any better.

> +			for_each_pipe_with_single_output(&data.display, pipe, output)
> +				igt_dynamic_f("pipe-%s-%s-plane-up-up-scaling",
> +					      kmstest_pipe_name(pipe), igt_output_name(output))
> +					test_plane_scaling_combo(&data, pipe, output, TEST_UP_UP_SCALING);
> +		}
> +
>  		igt_describe("Tests scaling with pixel formats.");
>  		igt_subtest_with_dynamic("scaler-with-pixel-format") {
>  			for_each_pipe_with_single_output(&data.display, pipe, output)
> -- 
> 2.25.1

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2022-02-09  8:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08  5:50 [igt-dev] [v3 0/9] Addition of new plane scaling test cases Swati Sharma
2022-02-08  5:50 ` [igt-dev] [v3 1/9] tests/kms_plane_scaling: Removal of plane-scaling subtest Swati Sharma
2022-02-08  5:50 ` [igt-dev] [v3 2/9] tests/kms_plane_scaling: Add output name in dynamic subtests Swati Sharma
2022-02-08  5:50 ` [igt-dev] [v3 3/9] tests/kms_plane_scaling: Upscaling each plane Swati Sharma
2022-02-09  8:26   ` Ville Syrjälä
2022-02-09  8:28     ` Sharma, Swati2
2022-02-08  5:50 ` [igt-dev] [v3 4/9] tests/kms_plane_scaling: Downscaling " Swati Sharma
2022-02-09  8:31   ` Ville Syrjälä
2022-02-14 16:40     ` Sharma, Swati2
2022-02-08  5:50 ` [igt-dev] [v3 5/9] tests/kms_plane_scaling: Upscaling on 2 planes Swati Sharma
2022-02-09  8:36   ` Ville Syrjälä [this message]
2022-02-14 16:42     ` Sharma, Swati2
2022-02-08  5:50 ` [igt-dev] [v3 6/9] tests/kms_plane_scaling: Downscaling " Swati Sharma
2022-02-08  5:50 ` [igt-dev] [v3 7/9] tests/kms_plane_scaling: Upscaling and downscaling scenario Swati Sharma
2022-02-08  5:50 ` [igt-dev] [v3 8/9] tests/kms_plane_scaling: Add negative test to check num of scalers Swati Sharma
2022-02-08  5:50 ` [igt-dev] [v3 9/9] tests/kms_plane_scaling: Refactor clipping-clamping subtest Swati Sharma
2022-02-08  6:25 ` [igt-dev] ✗ Fi.CI.BAT: failure for Addition of new plane scaling test cases (rev3) Patchwork
2022-02-08  9:47 ` [igt-dev] ✗ Fi.CI.BAT: failure for Addition of new plane scaling test cases (rev4) Patchwork
2022-02-08 22:04 ` [igt-dev] ✓ Fi.CI.BAT: success for Addition of new plane scaling test cases (rev5) Patchwork
2022-02-08 23:50 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=YgN9FpynUEiywoeL@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=swati2.sharma@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.