From: Ramalingam C <ramalingam.c@intel.com>
To: igt-dev@lists.freedesktop.org, daniel@ffwll.ch
Subject: [igt-dev] [PATCH i-g-t v4 3/4] kms_content_protection: Confirm that LIC is passed
Date: Fri, 8 Feb 2019 22:27:09 +0530 [thread overview]
Message-ID: <1549645030-7494-4-git-send-email-ramalingam.c@intel.com> (raw)
In-Reply-To: <1549645030-7494-1-git-send-email-ramalingam.c@intel.com>
Once the HDCP is enabled, kernel will run the link integrity check(LIC)
atleast once in 2Secs based on the HDCP versions.
So to confirm the link integrity check is passed, we oberve that HDCP
state remains ENABLED for next 4Secs.
v2:
Rebased.
Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
---
tests/kms_content_protection.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
index 7d82c733b378..c43e08b71a83 100644
--- a/tests/kms_content_protection.c
+++ b/tests/kms_content_protection.c
@@ -214,6 +214,14 @@ static bool igt_pipe_is_free(igt_display_t *display, enum pipe pipe)
return true;
}
+static void test_cp_lic(igt_output_t *output)
+{
+ bool ret;
+
+ /* Wait for 4Secs (min 2 cycles of Link Integrity Check) */
+ ret = wait_for_prop_value(output, 1, 4 * 1000);
+ igt_assert_f(!ret, "Content Protection LIC Failed\n");
+}
static void test_content_protection_on_output(igt_output_t *output,
enum igt_commit_style s,
@@ -239,6 +247,7 @@ static void test_content_protection_on_output(igt_output_t *output,
modeset_with_fb(pipe, output, s);
test_cp_enable_with_retry(output, s, 3);
+ test_cp_lic(output);
if (dpms_test) {
igt_pipe_set_prop_value(display, pipe,
--
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-02-08 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 16:57 [igt-dev] [PATCH i-g-t v4 0/4] HDCP test on modeset Ramalingam C
2019-02-08 16:57 ` [igt-dev] [PATCH i-g-t v4 1/4] kms_content_protection: modularizing the CP test steps Ramalingam C
2019-02-08 16:57 ` [igt-dev] [PATCH i-g-t v4 2/4] kms_content_protection: Test CP along with modeset Ramalingam C
2019-02-08 16:57 ` Ramalingam C [this message]
2019-02-08 16:57 ` [igt-dev] [PATCH i-g-t v4 4/4] kms_content_protection: Macros repalces the constants Ramalingam C
2019-02-11 17:26 ` Daniel Vetter
2019-02-08 17:41 ` [igt-dev] ✓ Fi.CI.BAT: success for HDCP test on modeset Patchwork
2019-02-08 22:10 ` [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=1549645030-7494-4-git-send-email-ramalingam.c@intel.com \
--to=ramalingam.c@intel.com \
--cc=daniel@ffwll.ch \
--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