Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Wentland <harry.wentland@amd.com>
To: Maxime Ripard <maxime@cerno.tech>, Alex Hung <alex.hung@amd.com>
Cc: igt-dev@lists.freedesktop.org, brian.starkey@arm.com
Subject: Re: [igt-dev] [PATCH 3/3] tests/kms_writeback: support DRM_FORMAT_XRGB2101010 for writeback
Date: Tue, 22 Aug 2023 10:34:51 -0400	[thread overview]
Message-ID: <eac5d9ed-4e76-41f1-aacb-f53e14fb7845@amd.com> (raw)
In-Reply-To: <k6cahbb4qc3pxiyexroh2egb7dhrb4ljf6hqaffdwrmsfxzkzg@xjifh5hbu5bt>



On 2023-08-22 10:14, Maxime Ripard wrote:
> On Thu, Aug 17, 2023 at 10:22:56AM -0600, Alex Hung wrote:
>>>>>> I think we should make a proper test for that format, instead of a
>>>>>> (silent) fallback?
>>>>>
>>>>> Not sure what's the proper test or the fallback you are referring to. The
>>>>> intention here is to test XRGB2101010 when possible without breaking the
>>>>> original behaviours for XRGB8888.
>>>>
>>>> Right, but you're not even testing that XRGB2101010 is actually there,
>>>> so if amdgpu format listing was somehow broken and you were to expose
>>>> XRGB8888 instead of XRGB2101010, you wouldn't notice. That's not great.
>>
>> Only XRGB2101010 is supported.
>>
>>>>> Changing kms_writeback to tests multiple formats requires significant
>>>>> modifications and tests which requires a driver capable of multiple formats
>>>>> in the first place.
>>>>
>>>> That's fine, amdgpu will be that driver.
>>
>> The purpose of this patch is to improve kms_writeback coverage:
>>
>> - check XRGB8888, and test if supported or skip otherwise
>> to
>> - no XRGB8888? also check XRGB2101010, and test if supported or skip
>> otherwise
>>
>> For amdgpu, no writeback -> support XRGB2101010 in writeback.
>>
>> XRGB2101010 will be used for testing. XRGB8888 may or may not be added later
>> depending on whether there will be consumers of the feature but that is out
>> of scope of this IGT patch.
> 
> My point is the fallback doesn't provide anything, and is harmful to
> some extent. So far, we have some hardware that support XRGB8888 only,
> and some that support XRGB2101010 only.
> 
> There's no point in falling back from one to the other, and if we ever
> have hardware that would support both it prevents from checking both.
> 
> And sure, we could address it then, or we could address it now. It's
> just adding an extra parameter to a couple of functions and a few new
> subtests, it's not like we need to rewrite the whole thing.
> 

I tend to agree. My preference would be to have a subtest for each
supported format, i.e. a -xrgb8888 and an -xrgb2101010 test.

I think there was some concern about not changing existing test
names. In that case we can keep the original test names for the
-xrgb8888 tests and append the format to the new tests.

Harry

> Maxime

  reply	other threads:[~2023-08-22 14:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 20:53 [igt-dev] [PATCH 1/3] lib/igt_fb: use the entire 32 bit for fnv1a_crc Alex Hung
2023-08-16 20:53 ` [igt-dev] [PATCH 2/3] lib/igt_fb: add 10 bits (XRGB2101010) supports in fnv1a_crc Alex Hung
2023-08-16 20:53 ` [igt-dev] [PATCH 3/3] tests/kms_writeback: support DRM_FORMAT_XRGB2101010 for writeback Alex Hung
2023-08-17  6:32   ` Maxime Ripard
2023-08-17  7:09     ` Alex Hung
2023-08-17  7:50       ` Maxime Ripard
2023-08-17 14:15         ` Harry Wentland
2023-08-17 16:22           ` Alex Hung
2023-08-22 14:14             ` Maxime Ripard
2023-08-22 14:34               ` Harry Wentland [this message]
2023-08-22 13:26           ` Maxime Ripard
2023-08-22 14:51             ` Harry Wentland
2023-08-16 23:41 ` [igt-dev] ○ CI.xeBAT: info for series starting with [1/3] lib/igt_fb: use the entire 32 bit for fnv1a_crc Patchwork
2023-08-16 23:47 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-08-17 11:13 ` [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=eac5d9ed-4e76-41f1-aacb-f53e14fb7845@amd.com \
    --to=harry.wentland@amd.com \
    --cc=alex.hung@amd.com \
    --cc=brian.starkey@arm.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=maxime@cerno.tech \
    /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