From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
To: Jeevan B <jeevan.b@intel.com>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 5/5] tests/kms_plane_scaling: Adding Tile-4 support
Date: Tue, 15 Mar 2022 18:01:37 +0200 [thread overview]
Message-ID: <c258c5bf-e1bd-bf62-8a7e-2f26e261077d@gmail.com> (raw)
In-Reply-To: <20220309164452.8240-6-jeevan.b@intel.com>
On 9.3.2022 18.44, Jeevan B wrote:
> Adding subtest to test new tiling format
>
> Signed-off-by: Jeevan B <jeevan.b@intel.com>
> ---
> tests/kms_plane_scaling.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
> index b91039b0..73975480 100644
> --- a/tests/kms_plane_scaling.c
> +++ b/tests/kms_plane_scaling.c
> @@ -40,6 +40,7 @@ typedef struct {
> igt_display_t display;
> struct igt_fb fb[4];
> bool extended;
> + bool has_4tile;
this entire has_4tile flag seems mostly harmful. Only place where it is
used is followed by igt_plane_has_format_mod(..)
> } data_t;
>
> const struct {
> @@ -331,7 +332,8 @@ static const uint64_t modifiers[] = {
> DRM_FORMAT_MOD_LINEAR,
> I915_FORMAT_MOD_X_TILED,
> I915_FORMAT_MOD_Y_TILED,
> - I915_FORMAT_MOD_Yf_TILED
> + I915_FORMAT_MOD_Yf_TILED,
> + I915_FORMAT_MOD_4_TILED
> };
>
> static void test_scaler_with_pixel_format_pipe(data_t *d, int width, int height, bool is_upscale,
> @@ -350,6 +352,10 @@ static void test_scaler_with_pixel_format_pipe(data_t *d, int width, int height,
>
> for (int i = 0; i < ARRAY_SIZE(modifiers); i++) {
> uint64_t modifier = modifiers[i];
> +
> + if (modifier == I915_FORMAT_MOD_4_TILED)
> + igt_require(d->has_4tile);
> +
I think this will cause this test to skip on all non dg2 boxes?
> struct igt_vec tested_formats;
>
> igt_vec_init(&tested_formats, sizeof(uint32_t));
> @@ -682,6 +688,9 @@ igt_main_args("", long_opts, help_str, opt_handler, &data)
> data.devid = is_i915_device(data.drm_fd) ?
> intel_get_drm_devid(data.drm_fd) : 0;
> igt_require(data.display.is_atomic);
> +
> + data.has_4tile = is_i915_device(data.drm_fd) &&
> + intel_get_device_info(intel_get_drm_devid(data.drm_fd))->has_4tile;
> }
>
> igt_subtest_group {
next prev parent reply other threads:[~2022-03-15 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 16:44 [igt-dev] [PATCH i-g-t 0/5] Add tile 4 plane format support Jeevan B
2022-03-09 16:44 ` [igt-dev] [PATCH i-g-t 1/5] lib/igt_draw: Use XY_FAST_COLOR_BLT on DG2 Jeevan B
2022-03-15 15:59 ` Juha-Pekka Heikkila
2022-03-09 16:44 ` [igt-dev] [PATCH i-g-t 2/5] igt/tests: Add support for Tile4(TileF) format to tests/kms_addfb_basic Jeevan B
2022-03-15 15:59 ` Juha-Pekka Heikkila
2022-03-09 16:44 ` [igt-dev] [PATCH i-g-t 3/5] tests/kms_frontbuffer_tracking: Add support for 4 tiling Jeevan B
2022-03-15 16:00 ` Juha-Pekka Heikkila
2022-03-09 16:44 ` [igt-dev] [PATCH i-g-t 4/5] tests/kms_draw_crc: Use 4 tiling when filling framebuffer Jeevan B
2022-03-15 16:00 ` Juha-Pekka Heikkila
2022-03-09 16:44 ` [igt-dev] [PATCH i-g-t 5/5] tests/kms_plane_scaling: Adding Tile-4 support Jeevan B
2022-03-15 16:01 ` Juha-Pekka Heikkila [this message]
2022-03-09 18:16 ` [igt-dev] ✓ Fi.CI.BAT: success for Add tile 4 plane format support Patchwork
2022-03-10 4:11 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=c258c5bf-e1bd-bf62-8a7e-2f26e261077d@gmail.com \
--to=juhapekka.heikkila@gmail.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jeevan.b@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