From: Suraj Kandpal <suraj.kandpal@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH i-g-t] tests/kms_content_protection: Add LIC Type 1 scenario
Date: Fri, 12 Jan 2024 16:03:31 +0530 [thread overview]
Message-ID: <20240112103330.169688-1-suraj.kandpal@intel.com> (raw)
Currently LIC is done only for type0 content this patch
adds LIC for type1 content too.
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
---
tests/kms_content_protection.c | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
index 6d472ee02..38e4143c8 100644
--- a/tests/kms_content_protection.c
+++ b/tests/kms_content_protection.c
@@ -43,8 +43,11 @@
#include "igt_kmod.h"
/**
- * SUBTEST: lic
- * Description: Test for the integrity of link.
+ * SUBTEST: lic-type-0
+ * Description: Test for the integrity of link for type 0 content.
+ *
+ * SUBTEST: lic-type-1
+ * Description: Test for the integrity of link for type 1 content.
*
* SUBTEST: content-type-change
* Description: Test the content type change when the content protection already
@@ -783,11 +786,16 @@ static const struct {
.cp_tests = CP_DPMS,
.content_type = HDCP_CONTENT_TYPE_0
},
- { .desc = "Test for the integrity of link.",
- .name = "lic",
+ { .desc = "Test for the integrity of link with type 0 content.",
+ .name = "lic-type-0",
.cp_tests = CP_LIC,
.content_type = HDCP_CONTENT_TYPE_0,
},
+ { .desc = "Test for the integrity of link with type 1 content",
+ .name = "lic-type-1",
+ .cp_tests = CP_LIC,
+ .content_type = HDCP_CONTENT_TYPE_1,
+ },
{ .desc = "Test content protection with content type 1 "
"that can be handled only through HDCP2.2.",
.name = "type1",
--
2.25.1
next reply other threads:[~2024-01-12 10:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 10:33 Suraj Kandpal [this message]
2024-01-12 11:23 ` ✓ Fi.CI.BAT: success for tests/kms_content_protection: Add LIC Type 1 scenario Patchwork
2024-01-12 11:40 ` ✓ CI.xeBAT: " Patchwork
2024-01-12 14:04 ` ✓ Fi.CI.IGT: " Patchwork
2024-01-16 9:34 ` [PATCH i-g-t] " Nautiyal, Ankit K
2024-01-16 9:34 ` Nautiyal, Ankit K
2024-01-16 9:48 ` Sharma, Swati2
2024-01-16 9:51 ` Kandpal, Suraj
2024-01-16 11:23 ` Suraj Kandpal
2024-01-17 11:28 ` Sharma, Swati2
2024-01-18 7:27 ` Suraj Kandpal
2024-01-18 7:33 ` Sharma, Swati2
2024-01-16 11:43 ` ✗ Fi.CI.BUILD: failure for tests/kms_content_protection: Add LIC Type 1 scenario (rev2) Patchwork
2024-01-16 11:48 ` ✗ GitLab.Pipeline: warning " Patchwork
2024-01-18 8:13 ` ✓ CI.xeBAT: success for tests/kms_content_protection: Add LIC Type 1 scenario (rev3) Patchwork
2024-01-18 8:33 ` ✗ Fi.CI.BAT: 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=20240112103330.169688-1-suraj.kandpal@intel.com \
--to=suraj.kandpal@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