From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 3/3] tests/kms_plane: Throw away yet another bi
Date: Fri, 28 Jun 2019 22:44:38 +0300 [thread overview]
Message-ID: <20190628194438.2714-4-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20190628194438.2714-1-ville.syrjala@linux.intel.com>
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
CHV pipe A/C sprites are causing a crc mismatch with BT.601
when we keep the six msbs. If we throw away one more bit we get
matches for BT.601. BT.709 matches even with 6 bits, as do the
pipe B planes with their programmable CSC. Also IVB and KBL
were both happy with 6 bits, so doesn't seem that that these
CHV mismatches are due to bugs in our code, just the hw is
a bit imprecise.
Cc: Uma Shankar <uma.shankar@intel.com>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
tests/kms_plane.c | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/tests/kms_plane.c b/tests/kms_plane.c
index 13d36254dfe3..e4f3b8d68748 100644
--- a/tests/kms_plane.c
+++ b/tests/kms_plane.c
@@ -30,6 +30,13 @@
#include <stdio.h>
#include <string.h>
+/*
+ * Throw away enough lsbs in pixel formats tests
+ * to get a match despite some differences between
+ * the software and hardware YCbCr<->RGB conversion
+ * routines.
+ */
+#define LUT_MASK 0xf800
typedef struct {
float red;
@@ -690,7 +697,7 @@ static bool test_format_plane(data_t *data, enum pipe pipe,
continue;
if (format == DRM_FORMAT_C8) {
- if (!set_c8_legacy_lut(data, pipe, 0xfc00))
+ if (!set_c8_legacy_lut(data, pipe, LUT_MASK))
continue;
} else {
if (!igt_fb_supported_format(format))
@@ -709,7 +716,7 @@ static bool test_format_plane(data_t *data, enum pipe pipe,
ref_crc, &fb);
if (format == DRM_FORMAT_C8)
- set_legacy_lut(data, pipe, 0xfc00);
+ set_legacy_lut(data, pipe, LUT_MASK);
}
igt_pipe_crc_stop(data->pipe_crc);
@@ -744,7 +751,7 @@ test_pixel_formats(data_t *data, enum pipe pipe)
igt_display_commit2(&data->display, data->display.is_atomic ? COMMIT_ATOMIC : COMMIT_LEGACY);
- set_legacy_lut(data, pipe, 0xfc00);
+ set_legacy_lut(data, pipe, LUT_MASK);
test_init(data, pipe);
--
2.21.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-06-28 19:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 19:44 [igt-dev] [PATCH i-g-t 0/3] Test all YCbCr encodings/ranges Ville Syrjala
2019-06-28 19:44 ` [igt-dev] [PATCH i-g-t 1/3] lib/igt_fb: Allow creating yuv fbs with different encodings/ranges Ville Syrjala
2019-07-02 14:47 ` Shankar, Uma
2019-07-02 17:56 ` [igt-dev] [PATCH i-g-t v2 " Ville Syrjala
2019-06-28 19:44 ` [igt-dev] [PATCH i-g-t 2/3] tests/kms_plane: Test all YCbCr encodings/ranges Ville Syrjala
2019-07-02 15:09 ` Shankar, Uma
2019-07-02 17:57 ` [igt-dev] [PATCH i-g-t v2 " Ville Syrjala
2019-07-02 18:07 ` Kazlauskas, Nicholas
2019-07-03 17:12 ` Ville Syrjälä
2019-07-03 18:01 ` Kazlauskas, Nicholas
2019-06-28 19:44 ` Ville Syrjala [this message]
2019-07-02 13:20 ` [igt-dev] [PATCH i-g-t 3/3] tests/kms_plane: Throw away yet another bi Kazlauskas, Nicholas
2019-07-02 13:30 ` Ville Syrjälä
2019-07-02 16:44 ` Shankar, Uma
2019-07-02 17:04 ` Ville Syrjälä
2019-07-03 12:41 ` Shankar, Uma
2019-06-28 22:48 ` [igt-dev] ✓ Fi.CI.BAT: success for Test all YCbCr encodings/ranges Patchwork
2019-06-29 9:45 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-07-02 17:57 ` [igt-dev] ✗ Fi.CI.BAT: failure for Test all YCbCr encodings/ranges (rev2) Patchwork
2019-07-02 18:08 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2019-07-02 18:28 ` [igt-dev] ✓ Fi.CI.BAT: success for Test all YCbCr encodings/ranges (rev3) Patchwork
2019-07-03 16:53 ` [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=20190628194438.2714-4-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.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