From: Nidhi Gupta <nidhi1.gupta@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Nidhi Gupta <nidhi1.gupta@intel.com>
Subject: [igt-dev] [PATCH i-g-t] tests/kms_content_protection : Added subtest description
Date: Tue, 6 Apr 2021 10:19:09 +0530 [thread overview]
Message-ID: <20210406044909.20915-1-nidhi1.gupta@intel.com> (raw)
Added subtest description.
Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com>
---
tests/kms_content_protection.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
index 0fdbacdd..5a75b871 100644
--- a/tests/kms_content_protection.c
+++ b/tests/kms_content_protection.c
@@ -735,46 +735,58 @@ igt_main
create_fbs();
}
+ igt_describe("Test content protection with legacy style commit.");
igt_subtest("legacy") {
data.cp_tests = 0;
test_content_protection(COMMIT_LEGACY, HDCP_CONTENT_TYPE_0);
}
+ igt_describe("Test content protection with atomic modesetting");
igt_subtest("atomic") {
igt_require(data.display.is_atomic);
data.cp_tests = 0;
test_content_protection(COMMIT_ATOMIC, HDCP_CONTENT_TYPE_0);
}
+ igt_describe("Test content protection with DPMS ON/OFF during atomic modesetting.");
igt_subtest("atomic-dpms") {
igt_require(data.display.is_atomic);
data.cp_tests = CP_DPMS;
test_content_protection(COMMIT_ATOMIC, HDCP_CONTENT_TYPE_0);
}
+ igt_describe("Test for the integrity of link.");
igt_subtest("LIC") {
igt_require(data.display.is_atomic);
data.cp_tests = CP_LIC;
test_content_protection(COMMIT_ATOMIC, HDCP_CONTENT_TYPE_0);
}
+ igt_describe("Test content protection with content type 1 that "
+ "can be handled only through HDCP2.2.");
igt_subtest("type1") {
igt_require(data.display.is_atomic);
test_content_protection(COMMIT_ATOMIC, HDCP_CONTENT_TYPE_1);
}
+ igt_describe("Test the teardown and rebuild of the interface between "
+ "I915 and mei hdcp.");
igt_subtest("mei_interface") {
igt_require(data.display.is_atomic);
data.cp_tests = CP_MEI_RELOAD;
test_content_protection(COMMIT_ATOMIC, HDCP_CONTENT_TYPE_1);
}
+ igt_describe("Test the content type change when the content protection already "
+ "enabled.");
igt_subtest("content_type_change") {
igt_require(data.display.is_atomic);
data.cp_tests = CP_TYPE_CHANGE;
test_content_protection(COMMIT_ATOMIC, HDCP_CONTENT_TYPE_1);
}
+ igt_describe("Test to detect the HDCP status change when we are reading the uevent "
+ "sent with the corresponding connector id and property id.");
igt_subtest("uevent") {
igt_require(data.display.is_atomic);
data.cp_tests = CP_UEVENT;
@@ -792,6 +804,8 @@ igt_main
* either of these options, we test SRM writing from userspace and
* validation of the same at kernel. Something is better than nothing.
*/
+ igt_describe("This test writes the facsimile SRM into the /lib/firmware/ "
+ "and check the kernel parsing of it by invoking the hdcp authentication.");
igt_subtest("srm") {
bool ret;
--
2.26.2
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2021-04-06 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 4:49 Nidhi Gupta [this message]
2021-04-06 7:04 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_content_protection : Added subtest description Patchwork
2021-04-06 10:20 ` [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=20210406044909.20915-1-nidhi1.gupta@intel.com \
--to=nidhi1.gupta@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.