diff options
| author | Maxime Ripard <maxime@cerno.tech> | 2022-03-08 15:40:38 +0100 |
|---|---|---|
| committer | Maxime Ripard <maxime@cerno.tech> | 2022-06-28 15:56:16 +0200 |
| commit | 35840762d3ee78e146a5a02aa6fe14dd7b4179a8 (patch) | |
| tree | 1e9197c3d66969c3cf7b77b824b59f83ba555695 | |
| parent | 85f4c1005150683397fd2775885067ce3515fe06 (diff) | |
tests/kms_writeback: Use a garbage X value to create fill our test buffer
Since we use buffers in XRGB8888, whatever value we have in X should be
ignored by the drivers and the hardware. However, since we always use
0xff in our test, whether that is the case or not cannot be determined.
Let's use a garbage value (but consistent across test runs) to make sure
it doesn't have any impact on the writeback output.
Acked-by: Pekka Paalanen <pekka.paalanen@collabora.com>
Signed-off-by: Maxime Ripard <maxime@cerno.tech>
| -rw-r--r-- | tests/kms_writeback.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/kms_writeback.c b/tests/kms_writeback.c index cf70a28e..4c3919a9 100644 --- a/tests/kms_writeback.c +++ b/tests/kms_writeback.c @@ -265,7 +265,7 @@ static void writeback_sequence(igt_output_t *output, igt_plane_t *plane, igt_fb_t *in_fb, igt_fb_t *out_fbs[], int n_commits) { int i = 0; - uint32_t in_fb_colors[2] = { 0xffff0000, 0xff00ff00 }; + uint32_t in_fb_colors[2] = { 0x42ff0000, 0x4200ff00 }; uint32_t clear_color = 0xffffffff; igt_crc_t cleared_crc, out_expected; |