From: Simon Ser <simon.ser@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 3/3] lib/tests/igt_edid: check number of extensions
Date: Fri, 5 Jul 2019 16:08:39 +0300 [thread overview]
Message-ID: <20190705130839.5117-3-simon.ser@intel.com> (raw)
In-Reply-To: <20190705130839.5117-1-simon.ser@intel.com>
Make sure we don't miss an extension by verifying the EDID field.
Signed-off-by: Simon Ser <simon.ser@intel.com>
---
lib/tests/igt_edid.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/tests/igt_edid.c b/lib/tests/igt_edid.c
index e15748286ac0..fc98f1bb71ce 100644
--- a/lib/tests/igt_edid.c
+++ b/lib/tests/igt_edid.c
@@ -92,6 +92,9 @@ igt_simple_main
igt_assert_f(edid_block_checksum(edid),
"checksum failed on %s EDID", f->desc);
/* check extension blocks, if any */
+ igt_assert_f(edid[126] == f->exts,
+ "unexpected number of extensions on %s EDID",
+ f->desc);
for (i = 0; i < f->exts; i++)
igt_assert_f(edid_block_checksum(edid + (i + 1) * EDID_LENGTH),
"CEA block checksum failed on %s EDID", f->desc);
--
2.22.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-07-05 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 13:08 [igt-dev] [PATCH i-g-t 1/3] lib/igt_edid: add enum for HDMI VSDB video flags Simon Ser
2019-07-05 13:08 ` [igt-dev] [PATCH i-g-t 2/3] lib/igt_kms: add igt_kms_get_3d_edid Simon Ser
2019-07-05 13:08 ` Simon Ser [this message]
2019-07-05 14:05 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/3] lib/igt_edid: add enum for HDMI VSDB video flags Patchwork
2019-07-06 21:40 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-07-10 9:20 ` [igt-dev] [PATCH i-g-t 1/3] " Arkadiusz Hiler
2019-07-11 8:42 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/3] lib/igt_edid: add enum for HDMI VSDB video flags (rev2) 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=20190705130839.5117-3-simon.ser@intel.com \
--to=simon.ser@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