From: Alex Hung <alex.hung@amd.com>
To: Maxime Ripard <maxime@cerno.tech>
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: Thu, 17 Aug 2023 01:09:44 -0600 [thread overview]
Message-ID: <5cd3fc34-f6c7-21ff-f710-cb3f543fcb80@amd.com> (raw)
In-Reply-To: <5zt2ctyod27qaw7sld4ejvvemgxm6chh4dtf7cnjiil2rizksm@bfiezcb3zo3q>
On 2023-08-17 00:32, Maxime Ripard wrote:
> Hi,
>
> On Wed, Aug 16, 2023 at 02:53:16PM -0600, Alex Hung wrote:
>> Allow kms_writeback to run with DRM_FORMAT_XRGB8888 if supported
>> or to try DRM_FORMAT_XRGB2101010 if DRM_FORMAT_XRGB8888 is not
>> available.
>
> XRGB8888 is always supposed to be available, if it's not, it's a driver
> issue. Which means that XRGB2101010 will never actually be tested.
It is up to a device driver to support specific format(s), not necessary
an issue. At least for now amdgpu won't support XRGB8888 but XRGB2101010.
>
> 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.
Changing kms_writeback to tests multiple formats requires significant
modifications and tests which requires a driver capable of multiple
formats in the first place. Once we or anyone have such supports we can
come back to rework kms_writeback.
>
> Maxime
next prev parent reply other threads:[~2023-08-17 7:09 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 [this message]
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
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=5cd3fc34-f6c7-21ff-f710-cb3f543fcb80@amd.com \
--to=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