public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_plane: add source clamping test
Date: Wed, 21 Nov 2018 11:45:31 +0200	[thread overview]
Message-ID: <56c33340-230e-2096-0c9e-4ced6857130b@gmail.com> (raw)
In-Reply-To: <0245bf2e-3a86-32f1-d492-3edc16b185e8@linux.intel.com>

On 20.11.2018 13:30, Maarten Lankhorst wrote:
> Op 15-11-18 om 16:51 schreef Juha-Pekka Heikkila:
>> Add test which create fb bigger than plane and clamp fb from all sides.
>>
>> Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
>> ---
>>   tests/kms_plane.c | 28 ++++++++++++++++++++++++++--
>>   1 file changed, 26 insertions(+), 2 deletions(-)
>>
>> diff --git a/tests/kms_plane.c b/tests/kms_plane.c
>> index 45e0a30..d79c22e 100644
>> --- a/tests/kms_plane.c
>> +++ b/tests/kms_plane.c
>> @@ -41,6 +41,7 @@ typedef struct {
>>   	int drm_fd;
>>   	igt_display_t display;
>>   	igt_pipe_crc_t *pipe_crc;
>> +	uint32_t crop;
>>   } data_t;
>>   
>>   static color_t red   = { 1.0f, 0.0f, 0.0f };
>> @@ -412,12 +413,22 @@ static void test_format_plane_color(data_t *data, enum pipe pipe,
>>   	const color_t *c = &colors[color];
>>   	struct igt_fb old_fb = *fb;
>>   
>> -	igt_create_color_fb(data->drm_fd, width, height,
>> -			    format, LOCAL_DRM_FORMAT_MOD_NONE,
>> +	igt_create_color_fb(data->drm_fd, width+data->crop*2,
>> +			    height+data->crop*2, format,
>> +			    LOCAL_DRM_FORMAT_MOD_NONE,
>>   			    c->red, c->green, c->blue, fb);
>>   
>>   	igt_plane_set_fb(plane, fb);
>>   
>> +	/*
>> +	 * if clamping test
>> +	 */
>> +	if (width-data->crop != 0) {
> if (data->crop) ?

Oops, I have been sleeping here.

>> +		igt_plane_set_size(plane, width, height);
>> +		igt_fb_set_position(fb, plane, data->crop, data->crop);
>> +		igt_fb_set_size(fb, plane, width, height);
>> +	}
>> +
> 
> If you don't fill the color fb outside the visible boundaries with a different color, I don't think you're testing anything..
> 

That's a good idea. Originally I just thought if source clamping would 
ever fail it would produce some garbage. This is how IFT version of this 
test went but I don't think it ever got any reasonable results anyway.

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

  reply	other threads:[~2018-11-21  9:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15 15:51 [igt-dev] [PATCH i-g-t] tests/kms_plane: add source clamping test Juha-Pekka Heikkila
2018-11-15 16:16 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-11-15 19:40 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-11-20 11:30 ` [igt-dev] [PATCH i-g-t] " Maarten Lankhorst
2018-11-21  9:45   ` Juha-Pekka Heikkila [this message]
2018-11-22 16:45 ` Juha-Pekka Heikkila
2018-11-22 18:51   ` Maarten Lankhorst
2018-11-23 11:51 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane: add source clamping test (rev2) Patchwork
2018-11-23 12:40 ` [igt-dev] ✓ Fi.CI.IGT: " 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=56c33340-230e-2096-0c9e-4ced6857130b@gmail.com \
    --to=juhapekka.heikkila@gmail.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.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