From: Kevin Strasser <kevin.strasser@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH 3/3] tests/kms_plane_scaling: Skip testing unsupported fp16 features
Date: Fri, 5 Apr 2019 13:14:05 -0700 [thread overview]
Message-ID: <1554495245-27955-4-git-send-email-kevin.strasser@intel.com> (raw)
In-Reply-To: <1554495245-27955-1-git-send-email-kevin.strasser@intel.com>
Disallow Yf tiling and Y-tiled 90/270 rotation for fp16 on Intel hardware.
rfc2:
- Move check into can_rotate (Maarten)
- Use igt_plane_has_format_mod (Maarten)
v1:
- Drop Y tile check (Ville)
Signed-off-by: Kevin Strasser <kevin.strasser@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
tests/kms_plane_scaling.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
index 3364073..661af9a 100644
--- a/tests/kms_plane_scaling.c
+++ b/tests/kms_plane_scaling.c
@@ -174,12 +174,18 @@ static const igt_rotation_t rotations[] = {
IGT_ROTATION_270,
};
-static bool can_rotate(data_t *d, unsigned format)
+static bool can_rotate(data_t *d, unsigned format, uint64_t tiling,
+ igt_rotation_t rot)
{
if (format == DRM_FORMAT_C8 ||
(intel_gen(d->devid) < 11 && format == DRM_FORMAT_RGB565))
return false;
+ // Y-tiled 90/270 rotation isn't supported for fp16 on Intel
+ if (is_i915_device(d->drm_fd) && igt_format_is_fp16(format) &&
+ (rot == IGT_ROTATION_90 || rot == IGT_ROTATION_270))
+ return false;
+
return true;
}
@@ -200,8 +206,9 @@ static void test_scaler_with_rotation_pipe(data_t *d, enum pipe pipe,
igt_rotation_t rot = rotations[i];
for (int j = 0; j < plane->drm_plane->count_formats; j++) {
unsigned format = plane->drm_plane->formats[j];
+
if (igt_fb_supported_format(format) &&
- can_rotate(d, format))
+ can_rotate(d, format, tiling, rot))
check_scaling_pipe_plane_rot(d, plane, format,
tiling, pipe,
output, rot);
@@ -234,6 +241,9 @@ static void test_scaler_with_pixel_format_pipe(data_t *d, enum pipe pipe, igt_ou
for (int j = 0; j < plane->drm_plane->count_formats; j++) {
uint32_t format = plane->drm_plane->formats[j];
+ if (!igt_plane_has_format_mod(plane, format, tiling))
+ continue;
+
if (igt_fb_supported_format(format))
check_scaling_pipe_plane_rot(d, plane,
format, tiling,
--
2.7.4
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-04-05 20:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 20:14 [igt-dev] [PATCH 0/3] Add support for fp16 formats Kevin Strasser
2019-04-05 20:14 ` [igt-dev] [PATCH 1/3] lib: Add halffloat implementation Kevin Strasser
2019-04-24 20:05 ` Daniel Vetter
2019-04-24 20:19 ` Ville Syrjälä
2019-04-24 20:43 ` Strasser, Kevin
2019-04-25 7:34 ` Daniel Vetter
2019-04-05 20:14 ` [igt-dev] [PATCH 2/3] lib/igt_fb: Add support for fp16 formats through conversion Kevin Strasser
2019-04-05 20:14 ` Kevin Strasser [this message]
2019-04-09 8:17 ` [igt-dev] [PATCH 3/3] tests/kms_plane_scaling: Skip testing unsupported fp16 features Maarten Lankhorst
2019-04-11 22:36 ` Strasser, Kevin
2019-04-18 19:25 ` Ville Syrjälä
2019-04-05 20:35 ` [igt-dev] ✓ Fi.CI.BAT: success for Add support for fp16 formats Patchwork
2019-04-06 18:11 ` [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=1554495245-27955-4-git-send-email-kevin.strasser@intel.com \
--to=kevin.strasser@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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