Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Suraj Kandpal <suraj.kandpal@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: swati2.sharma@intel.com, santhosh.reddy.guddati@intel.com,
	Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH i-g-t 1/2] tests/kms_content_protection: Group all force_hdcp14 tests together
Date: Mon, 11 May 2026 09:11:37 +0530	[thread overview]
Message-ID: <20260511034137.93127-2-suraj.kandpal@intel.com> (raw)
In-Reply-To: <20260511034137.93127-1-suraj.kandpal@intel.com>

Change ordering of tests so that all force_hdcp14 test are run together,
that too after all the regular tests have been run.
Currently we are seeing these tests are putting MST DOCK in a bad state from
time to time where it can only report HDCP 1.4 after running these
tests.
The only exception here is the DPMS and suspend resume test which are
run last since the help MST DOCK to return back to good state.

Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
---
 tests/kms_content_protection.c | 64 +++++++++++++++++-----------------
 1 file changed, 32 insertions(+), 32 deletions(-)

diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
index a42f699e9..3baf225cd 100644
--- a/tests/kms_content_protection.c
+++ b/tests/kms_content_protection.c
@@ -1025,42 +1025,17 @@ static const struct {
 	bool content_type;
 	bool is_force_hdcp14;
 } subtests[] = {
-	{ .desc = "Test content protection with atomic modesetting with HDCP1.4.",
-	  .name = "atomic-hdcp14",
-	  .cp_tests = 0,
-	  .content_type = HDCP_CONTENT_TYPE_0,
-	  .is_force_hdcp14 = true,
-	},
 	{ .desc = "Test content protection with atomic modesetting",
 	  .name = "atomic",
 	  .cp_tests = 0,
 	  .content_type = HDCP_CONTENT_TYPE_0,
 	  .is_force_hdcp14 = false,
 	},
-	{ .desc = "Test content protection with DPMS ON/OFF during "
-		  "atomic modesetting with HDCP1.4.",
-	  .name = "atomic-dpms-hdcp14",
-	  .cp_tests = CP_DPMS,
-	  .content_type = HDCP_CONTENT_TYPE_0,
-	  .is_force_hdcp14 = true,
-	},
-	{ .desc = "Test content protection with DPMS ON/OFF during atomic modesetting.",
-	  .name = "atomic-dpms",
-	  .cp_tests = CP_DPMS,
-	  .content_type = HDCP_CONTENT_TYPE_0,
-	  .is_force_hdcp14 = false,
-	},
 	{ .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 0 content.",
-	  .name = "lic-type-0-hdcp14",
-	  .cp_tests = CP_LIC,
-	  .content_type = HDCP_CONTENT_TYPE_0,
-	  .is_force_hdcp14 = true,
-	},
 	{ .desc = "Test for the integrity of link with type 1 content",
 	  .name = "lic-type-1",
 	  .cp_tests = CP_LIC,
@@ -1093,13 +1068,6 @@ static const struct {
 	  .content_type = HDCP_CONTENT_TYPE_0,
 	  .is_force_hdcp14 = false,
 	},
-	{ .desc = "Test to detect the HDCP status change when we are reading the uevent "
-		  "sent with the corresponding connector id and property id.",
-	  .name = "uevent-hdcp14",
-	  .cp_tests = CP_UEVENT,
-	  .content_type = HDCP_CONTENT_TYPE_0,
-	  .is_force_hdcp14 = true,
-	},
 	/*
 	 *  Testing the revocation check through SRM needs a HDCP sink with
 	 *  programmable Ksvs or we need a uAPI from kernel to read the
@@ -1115,6 +1083,38 @@ static const struct {
 	  .content_type = HDCP_CONTENT_TYPE_0,
 	  .is_force_hdcp14 = false,
 	},
+	{ .desc = "Test content protection with atomic modesetting with HDCP1.4.",
+	  .name = "atomic-hdcp14",
+	  .cp_tests = 0,
+	  .content_type = HDCP_CONTENT_TYPE_0,
+	  .is_force_hdcp14 = true,
+	},
+	{ .desc = "Test for the integrity of link with type 0 content.",
+	  .name = "lic-type-0-hdcp14",
+	  .cp_tests = CP_LIC,
+	  .content_type = HDCP_CONTENT_TYPE_0,
+	  .is_force_hdcp14 = true,
+	},
+	{ .desc = "Test to detect the HDCP status change when we are reading the uevent "
+		  "sent with the corresponding connector id and property id.",
+	  .name = "uevent-hdcp14",
+	  .cp_tests = CP_UEVENT,
+	  .content_type = HDCP_CONTENT_TYPE_0,
+	  .is_force_hdcp14 = true,
+	},
+	{ .desc = "Test content protection with DPMS ON/OFF during "
+		  "atomic modesetting with HDCP1.4.",
+	  .name = "atomic-dpms-hdcp14",
+	  .cp_tests = CP_DPMS,
+	  .content_type = HDCP_CONTENT_TYPE_0,
+	  .is_force_hdcp14 = true,
+	},
+	{ .desc = "Test content protection with DPMS ON/OFF during atomic modesetting.",
+	  .name = "atomic-dpms",
+	  .cp_tests = CP_DPMS,
+	  .content_type = HDCP_CONTENT_TYPE_0,
+	  .is_force_hdcp14 = false,
+	},
 	{.desc = "Test to verify the behaviour of HDCP after suspend resume cycles.",
 	 .name = "suspend-resume",
 	 .cp_tests = SUSPEND_RESUME,
-- 
2.34.1


  reply	other threads:[~2026-05-11  3:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11  3:41 [PATCH i-g-t 0/2] Group all force_hdcp14 tests together Suraj Kandpal
2026-05-11  3:41 ` Suraj Kandpal [this message]
2026-05-12  4:43   ` [PATCH i-g-t 1/2] tests/kms_content_protection: " Reddy Guddati, Santhosh
2026-05-11  3:41 ` [PATCH i-g-t 2/2] tests/kms_content_protection: Group all MST " Suraj Kandpal
2026-05-12  4:45   ` Reddy Guddati, Santhosh
2026-05-11 21:23 ` ✓ i915.CI.BAT: success for Group all " Patchwork
2026-05-11 21:55 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-11 23:52 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-12  5:02 ` ✗ i915.CI.Full: " 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=20260511034137.93127-2-suraj.kandpal@intel.com \
    --to=suraj.kandpal@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=santhosh.reddy.guddati@intel.com \
    --cc=swati2.sharma@intel.com \
    /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