public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ramalingam C <ramalingam.c@intel.com>
To: igt-dev <igt-dev@lists.freedesktop.org>
Subject: [igt-dev] [PATCH i-g-t] kms_content_protection: add check for DPMS off state
Date: Fri,  3 Jan 2020 13:41:07 +0530	[thread overview]
Message-ID: <20200103081107.28144-1-ramalingam.c@intel.com> (raw)

During DPMS off HDCP state should be DESIRED.
Lets add a check for that.

Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
cc: Anshuman Gupta <anshuman.gupta@intel.com>
---
 tests/kms_content_protection.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
index 8b361fdefb2e..eb6cd9ec50b1 100644
--- a/tests/kms_content_protection.c
+++ b/tests/kms_content_protection.c
@@ -513,6 +513,11 @@ static void test_content_protection_on_output(igt_output_t *output,
 						IGT_CRTC_ACTIVE, 0);
 			igt_display_commit2(display, s);
 
+			/* Wait for HDCP to be disabled, before crtc off */
+			ret = wait_for_prop_value(output, CP_DESIRED,
+						  KERNEL_DISABLE_TIME_ALLOWED_MSEC);
+			igt_assert_f(ret, "Content Protection not cleared\n");
+
 			igt_pipe_set_prop_value(display, pipe,
 						IGT_CRTC_ACTIVE, 1);
 			igt_display_commit2(display, s);
-- 
2.20.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

             reply	other threads:[~2020-01-03  8:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03  8:11 Ramalingam C [this message]
2020-01-03  8:39 ` [igt-dev] ✗ GitLab.Pipeline: warning for kms_content_protection: add check for DPMS off state Patchwork
2020-01-03  8:49 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2020-01-03 10:45 ` [igt-dev] [PATCH i-g-t] " Gupta, Anshuman

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=20200103081107.28144-1-ramalingam.c@intel.com \
    --to=ramalingam.c@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