From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
Cc: igt-dev@lists.freedesktop.org, "Naladala,
Ramanaidu" <Ramanaidu.naladala@intel.com>
Subject: Re: [PATCH i-g-t v2] tests/kms_rotation_crc: Intel display version 20 onwards doesn't do hflip with tile4
Date: Wed, 30 Oct 2024 00:02:06 +0200 [thread overview]
Message-ID: <ZyFbXl06g_94aoNy@intel.com> (raw)
In-Reply-To: <20241022094744.3884409-1-juhapekka.heikkila@gmail.com>
On Tue, Oct 22, 2024 at 12:47:44PM +0300, Juha-Pekka Heikkila wrote:
> On Intel display version 20 Tile4 no longer can be used with horizontal
> flip.
>
> Bspec: 69853
>
> Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> ---
> tests/kms_rotation_crc.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/tests/kms_rotation_crc.c b/tests/kms_rotation_crc.c
> index 9888ac6ac..d4a1c91cc 100644
> --- a/tests/kms_rotation_crc.c
> +++ b/tests/kms_rotation_crc.c
> @@ -639,6 +639,14 @@ static void test_plane_rotation(data_t *data, int plane_type, bool test_bad_form
> !IS_CHERRYVIEW(data->devid) ||
> data->rotation != (IGT_ROTATION_180 | IGT_REFLECT_X));
>
> + /* Intel display version 20 onwards cannot do reflect-x with
> + * tile4
> + */
> + igt_require(!is_intel_device(data->gfx_fd) ||
> + intel_display_ver(data->devid) < 20 ||
> + !(data->override_modifier == I915_FORMAT_MOD_4_TILED &&
> + data->rotation & IGT_REFLECT_X));
> +
This place is getting rather cluttered. Can you extract all the
igt_require() conditions here into a separate function so we'd
just be left with something like
igt_require(plane_can_rotate(...)); ?
> prepare_crtc(data, output, pipe, plane, true);
>
> for (i = 0; i < num_rectangle_types; i++) {
> --
> 2.45.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2024-10-29 22:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 9:47 [PATCH i-g-t v2] tests/kms_rotation_crc: Intel display version 20 onwards doesn't do hflip with tile4 Juha-Pekka Heikkila
2024-10-22 15:04 ` ✗ Fi.CI.BAT: failure for " Patchwork
2024-10-22 15:19 ` ✓ CI.xeBAT: success " Patchwork
2024-10-22 17:09 ` ✗ CI.xeFULL: failure " Patchwork
2024-10-25 10:49 ` ✗ Fi.CI.BAT: failure for tests/kms_rotation_crc: Intel display version 20 onwards doesn't do hflip with tile4 (rev2) Patchwork
2024-10-25 11:04 ` ✓ CI.xeBAT: success " Patchwork
2024-10-26 22:02 ` ✗ CI.xeFULL: failure " Patchwork
2024-10-29 14:25 ` ✓ Fi.CI.BAT: success for tests/kms_rotation_crc: Intel display version 20 onwards doesn't do hflip with tile4 (rev3) Patchwork
2024-10-29 14:28 ` ✗ CI.xeBAT: failure " Patchwork
2024-10-29 15:57 ` ✗ CI.xeFULL: " Patchwork
2024-10-29 18:33 ` ✗ GitLab.Pipeline: warning for tests/kms_rotation_crc: Intel display version 20 onwards doesn't do hflip with tile4 (rev4) Patchwork
2024-10-29 18:53 ` ✓ CI.xeBAT: success " Patchwork
2024-10-29 18:54 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-10-29 19:07 ` ✗ Fi.CI.IGT: failure for tests/kms_rotation_crc: Intel display version 20 onwards doesn't do hflip with tile4 (rev3) Patchwork
2024-10-29 22:02 ` Ville Syrjälä [this message]
2024-10-29 22:35 ` ✗ CI.xeFULL: failure for tests/kms_rotation_crc: Intel display version 20 onwards doesn't do hflip with tile4 (rev4) 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=ZyFbXl06g_94aoNy@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=Ramanaidu.naladala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juhapekka.heikkila@gmail.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