Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Sean Paul <sean@poorly.run>, <igt-dev@lists.freedesktop.org>
Cc: Sean Paul <seanpaul@chromium.org>
Subject: Re: [igt-dev] [PATCH 5/6] tests/kms_vrr: Change the pattern displayed in the test
Date: Thu, 7 Sep 2023 00:38:17 +0530	[thread overview]
Message-ID: <331035f9-0307-21dc-c19d-61708ef4a4fe@intel.com> (raw)
In-Reply-To: <20230825183934.1271156-6-sean@poorly.run>


On Sat-26-08-2023 12:06 am, Sean Paul wrote:
> From: Sean Paul <seanpaul@chromium.org>
> 
> Upgrade the tiny box in the top left corner to some vertical color
> bars with horizontal grey and white bars at the bottom.
> 
> Cc: Mark Yacoub <markyacoub@chromium.org>
> Signed-off-by: Sean Paul <seanpaul@chromium.org>
> ---
>   tests/kms_vrr.c | 16 ++++++++++++----
>   1 file changed, 12 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/kms_vrr.c b/tests/kms_vrr.c
> index 67d13d4bf..e6820a0d1 100644
> --- a/tests/kms_vrr.c
> +++ b/tests/kms_vrr.c
> @@ -242,6 +242,7 @@ static void prepare_test(data_t *data, igt_output_t *output, enum pipe pipe)
>   {
>   	drmModeModeInfo mode;
>   	cairo_t *cr;
> +	int bar_width;
>   
>   	/* Reset output */
>   	igt_display_reset(&data->display);
> @@ -284,11 +285,18 @@ static void prepare_test(data_t *data, igt_output_t *output, enum pipe pipe)
>   			    DRM_FORMAT_XRGB8888, DRM_FORMAT_MOD_LINEAR,
>   			    0.50, 0.50, 0.50, &data->fb[1]);
>   
> +	bar_width = mode.hdisplay / 3;

I can fell, it would be better to fill the full screen.

ex:
remaining_rows = mode.hdisplay % 3;
and paint it with the last used colors (bar 3)

>   	cr = igt_get_cairo_ctx(data->drm_fd, &data->fb[0]);
> -
> -	igt_paint_color(cr, 0, 0, mode.hdisplay / 10, mode.vdisplay / 10,
> -			1.00, 0.00, 0.00);
> -
> +	for (int j = 0; j < 3; ++j) {
> +		unsigned int color = 1 << j;
> +		igt_paint_color(cr, bar_width * j, 0, bar_width,
> +				mode.vdisplay - 200,
------------------------------------------------^

> +				color >> 0 & 1,
> +				color >> 1 & 1,
> +				color >> 2 & 1);
> +	}
> +	igt_paint_color(cr, 0, mode.vdisplay - 100, mode.hdisplay, 100,
-----------------------------------------------^-------------------^
Instead of using these magic numbers, can't we measure like vidsplay/4 
or something like that?

- Bhanu

> +			1.00, 1.00, 1.00);
>   	igt_put_cairo_ctx(cr);
>   
>   	/* Take care of any required modesetting before the test begins. */

  reply	other threads:[~2023-09-06 19:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 18:36 [igt-dev] [PATCH 0/6] tests/kms_vrr: Modify kms_vrr to allow flicker Sean Paul
2023-08-25 18:36 ` [igt-dev] [PATCH 1/6] tests/kms_vrr: Move fb0 and fb1 to an array Sean Paul
2023-09-06 19:07   ` Modem, Bhanuprakash
2023-08-25 18:36 ` [igt-dev] [PATCH 2/6] tests/kms_vrr: Move vtest_ns into data_t Sean Paul
2023-09-06 19:07   ` Modem, Bhanuprakash
2023-08-25 18:36 ` [igt-dev] [PATCH 3/6] tests/kms_vrr: Allow test rate to be altered from the command line Sean Paul
2023-09-06 19:07   ` Modem, Bhanuprakash
2023-08-25 18:36 ` [igt-dev] [PATCH 4/6] tests/kms_vrr: Allow test duration to be specified " Sean Paul
2023-09-06 19:08   ` Modem, Bhanuprakash
2023-08-25 18:36 ` [igt-dev] [PATCH 5/6] tests/kms_vrr: Change the pattern displayed in the test Sean Paul
2023-09-06 19:08   ` Modem, Bhanuprakash [this message]
2023-08-25 18:36 ` [igt-dev] [PATCH 6/6] test/kms_vrr: Add ability to flip static image for flicker profiling Sean Paul
2023-08-25 19:30 ` [igt-dev] ✗ GitLab.Pipeline: warning for tests/kms_vrr: Modify kms_vrr to allow flicker Patchwork
2023-08-25 19:46 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-08-25 19:55 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-08-26 13:51 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-08-31 17:15 ` [igt-dev] [PATCH 0/6] " Sean Paul
2023-09-06 19:08 ` Modem, Bhanuprakash

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=331035f9-0307-21dc-c19d-61708ef4a4fe@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=sean@poorly.run \
    --cc=seanpaul@chromium.org \
    /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