Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sowmiya S <sowmiya.s@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: swati2.sharma@intel.com, karthik.b.s@intel.com,
	Sowmiya S <sowmiya.s@intel.com>
Subject: [PATCH i-g-t v2 3/3] tests/kms_feature_discovery: add hdcp capability discovery subtest
Date: Thu, 22 Oct 2026 16:20:58 +0530	[thread overview]
Message-ID: <20261022105102.384486-4-sowmiya.s@intel.com> (raw)
In-Reply-To: <20261022105102.384486-1-sowmiya.s@intel.com>

Add a "hdcp" subtest that reports whether at least one connected
output supports HDCP, using igt_hdcp_output_capable() from the
shared igt_hdcp library with IGT_HDCP_CONTENT_TYPE_0.

Signed-off-by: Sowmiya S <sowmiya.s@intel.com>
---
 tests/kms_feature_discovery.c | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/tests/kms_feature_discovery.c b/tests/kms_feature_discovery.c
index d18272b97..fdc48685f 100644
--- a/tests/kms_feature_discovery.c
+++ b/tests/kms_feature_discovery.c
@@ -36,6 +36,7 @@
 #ifdef HAVE_CHAMELIUM
 #include "igt_chamelium.h"
 #endif
+#include "igt_hdcp.h"
 #include "igt_hdr.h"
 #include "igt_kms.h"
 #include "igt_psr.h"
@@ -76,6 +77,10 @@
  * Description: Make sure that we have at least one DSC-capable sink.
  * Mega feature: VDSC
  *
+ * SUBTEST: hdcp
+ * Description: Make sure that we have at least one HDCP-capable output.
+ * Mega feature: HDCP
+ *
  * arg[1].values: 1, 2, 3, 4
  */
 
@@ -266,5 +271,26 @@ int igt_main() {
 				      "No DSC-capable sink found (checked %d outputs).\n",
 				      num_outputs);
 		}
+
+		igt_describe("Make sure that we have at least one HDCP-capable output.");
+		igt_subtest("hdcp") {
+			igt_output_t *output;
+			int num_outputs = 0;
+			bool found = false;
+
+			for_each_connected_output(&display, output) {
+				num_outputs++;
+				if (!igt_hdcp_output_capable(fd, output,
+							    IGT_HDCP_CONTENT_TYPE_0))
+					continue;
+
+				found = true;
+				break;
+			}
+
+			igt_require_f(found,
+				      "No HDCP-capable output found (checked %d outputs).\n",
+				      num_outputs);
+		}
 	}
 }
-- 
2.43.0


  parent reply	other threads:[~2026-10-22 10:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22 10:50 [PATCH i-g-t v2 0/3] lib/igt_hdcp: extract shared HDCP helpers from kms_content_protection Sowmiya S
2026-10-22 10:50 ` [PATCH i-g-t v2 1/3] lib/igt_hdcp: add shared HDCP helper library Sowmiya S
2026-10-22 10:50 ` [PATCH i-g-t v2 2/3] tests/kms_content_protection: use shared igt_hdcp library Sowmiya S
2026-10-22 10:50 ` Sowmiya S [this message]
2026-10-22 11:58 ` ✓ Xe.CI.BAT: success for lib/igt_hdcp: extract shared HDCP helpers from kms_content_protection (rev2) Patchwork
2026-10-22 12:39 ` ✓ i915.CI.BAT: " Patchwork
2026-10-22 18:01 ` ✓ Xe.CI.FULL: " Patchwork
2026-10-22 23:59 ` ✓ 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=20261022105102.384486-4-sowmiya.s@intel.com \
    --to=sowmiya.s@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=karthik.b.s@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