Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] lib/igt_fb: on Xe driver take into account adlp with no extended block copy
Date: Thu, 5 Oct 2023 15:35:23 +0300	[thread overview]
Message-ID: <660121ed-7973-6a64-209a-8186639db59e@gmail.com> (raw)
In-Reply-To: <20231005111009.3bhbl4qaz4pwlnir@kamilkon-desk.igk.intel.com>

Hi Kamil,

On 5.10.2023 14.10, Kamil Konieczny wrote:
> Hi Juha-Pekka,
> On 2023-10-04 at 16:47:22 +0300, Juha-Pekka Heikkila wrote:
> 
> Could you make your patch title a little shorter?
> 
> [PATCH i-g-t] lib/igt_fb: on Xe driver take into account adlp with no extended block copy
> 
> imho better:
> 
> [PATCH i-g-t] lib/igt_fb: fix for platforms with no extended block copy
> 

Alas I had already merged this because there were people asking to get 
it in.

>> With Xe add check to not use extended block copy if it is not available.
> ------ ^^
> Is it limited to Xe only?

This patch is only about Xe.

/Juha-Pekka

> 
> Regards,
> Kamil
> 
>>
>> Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
>> ---
>>   lib/igt_fb.c | 20 +++++++++++---------
>>   1 file changed, 11 insertions(+), 9 deletions(-)
>>
>> diff --git a/lib/igt_fb.c b/lib/igt_fb.c
>> index f0c0681ab..54a66eb6a 100644
>> --- a/lib/igt_fb.c
>> +++ b/lib/igt_fb.c
>> @@ -2920,17 +2920,19 @@ static void blitcopy(const struct igt_fb *dst_fb,
>>   			blt_set_copy_object(&blt.src, src);
>>   			blt_set_copy_object(&blt.dst, dst);
>>   
>> -			blt_set_object_ext(&ext.src,
>> -					   blt_compression_format(&blt, src_fb),
>> -					   src_fb->width, src_fb->height,
>> -					   SURFACE_TYPE_2D);
>> +			if (blt_uses_extended_block_copy(src_fb->fd)) {
>> +				blt_set_object_ext(&ext.src,
>> +						blt_compression_format(&blt, src_fb),
>> +						src_fb->width, src_fb->height,
>> +						SURFACE_TYPE_2D);
>>   
>> -			blt_set_object_ext(&ext.dst,
>> -					   blt_compression_format(&blt, dst_fb),
>> -					   dst_fb->width, dst_fb->height,
>> -					   SURFACE_TYPE_2D);
>> +				blt_set_object_ext(&ext.dst,
>> +						blt_compression_format(&blt, dst_fb),
>> +						dst_fb->width, dst_fb->height,
>> +						SURFACE_TYPE_2D);
>>   
>> -			pext = &ext;
>> +				pext = &ext;
>> +			}
>>   
>>   			blt_set_batch(&blt.bb, xe_bb, bb_size, mem_region);
>>   
>> -- 
>> 2.34.1
>>

      reply	other threads:[~2023-10-05 12:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 13:47 [igt-dev] [PATCH i-g-t] lib/igt_fb: on Xe driver take into account adlp with no extended block copy Juha-Pekka Heikkila
2023-10-04 16:41 ` Maarten Lankhorst
2023-10-05  8:39   ` Juha-Pekka Heikkila
2023-10-05 11:18     ` Zbigniew Kempczyński
2023-10-05 12:32       ` Juha-Pekka Heikkila
2023-10-04 17:24 ` Zbigniew Kempczyński
2023-10-04 18:06 ` [igt-dev] ✓ CI.xeBAT: success for " Patchwork
2023-10-04 18:07 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-10-05  4:01 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-05 11:10 ` [igt-dev] [PATCH i-g-t] " Kamil Konieczny
2023-10-05 12:35   ` Juha-Pekka Heikkila [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=660121ed-7973-6a64-209a-8186639db59e@gmail.com \
    --to=juhapekka.heikkila@gmail.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@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