All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suraj Kandpal <suraj.kandpal@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 02/10] drm/i915/hdcp: Move source hdcp2 checks into its own function
Date: Thu,  1 Feb 2024 01:09:21 +0530	[thread overview]
Message-ID: <20240131193929.938748-3-suraj.kandpal@intel.com> (raw)
In-Reply-To: <20240131193929.938748-1-suraj.kandpal@intel.com>

Move checks on the source side for HDCP2.2 into its own function
so that they can be used in the HDCP remote capability check
function.

Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
---
 drivers/gpu/drm/i915/display/intel_hdcp.c | 20 +++++++++++++++++---
 1 file changed, 17 insertions(+), 3 deletions(-)

diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c b/drivers/gpu/drm/i915/display/intel_hdcp.c
index c3e692e7f790..4593ac10e2fa 100644
--- a/drivers/gpu/drm/i915/display/intel_hdcp.c
+++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
@@ -160,12 +160,14 @@ bool intel_hdcp_capable(struct intel_connector *connector)
 	return capable;
 }
 
-/* Is HDCP2.2 capable on Platform and Sink */
-bool intel_hdcp2_capable(struct intel_connector *connector)
+/*
+ * Check if the source has all the building blocks ready to make
+ * HDCP 2.2 work
+ */
+static bool intel_hdcp2_prerequisite(struct intel_connector *connector)
 {
 	struct drm_i915_private *i915 = to_i915(connector->base.dev);
 	struct intel_hdcp *hdcp = &connector->hdcp;
-	bool capable = false;
 
 	/* I915 support for HDCP2.2 */
 	if (!hdcp->hdcp2_supported)
@@ -185,6 +187,18 @@ bool intel_hdcp2_capable(struct intel_connector *connector)
 	}
 	mutex_unlock(&i915->display.hdcp.hdcp_mutex);
 
+	return true;
+}
+
+/* Is HDCP2.2 capable on Platform and Sink */
+bool intel_hdcp2_capable(struct intel_connector *connector)
+{
+	struct intel_hdcp *hdcp = &connector->hdcp;
+	bool capable = false;
+
+	if (!intel_hdcp2_prerequisite(connector))
+		return false;
+
 	/* Sink's capability for HDCP2.2 */
 	hdcp->shim->hdcp_2_2_capable(connector, &capable);
 
-- 
2.25.1


  parent reply	other threads:[~2024-01-31 19:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 19:39 [PATCH 00/10] HDCP Type1 MST fixes Suraj Kandpal
2024-01-31 19:39 ` [PATCH 01/10] drm/i915/hdcp: Move to direct reads for HDCP Suraj Kandpal
2024-01-31 19:39 ` Suraj Kandpal [this message]
2024-02-02  4:30   ` [PATCH 02/10] drm/i915/hdcp: Move source hdcp2 checks into its own function Nautiyal, Ankit K
2024-01-31 19:39 ` [PATCH 03/10] drm/i915/hdcp: Refactor intel_dp_hdcp2_capable Suraj Kandpal
2024-02-02  4:31   ` Nautiyal, Ankit K
2024-02-02  4:33   ` Nautiyal, Ankit K
2024-01-31 19:39 ` [PATCH 04/10] drm/i915/hdcp: Pass drm_dp_aux to read_bcaps function Suraj Kandpal
2024-02-02  4:31   ` Nautiyal, Ankit K
2024-01-31 19:39 ` [PATCH 05/10] drm/i915/hdcp: Add new remote capability check shim function Suraj Kandpal
2024-01-31 19:39 ` [PATCH 06/10] drm/i915/hdcp: HDCP Capability for the downstream device Suraj Kandpal
2024-01-31 19:39 ` [PATCH 07/10] drm/i915/hdcp: Remove additional timing for reading mst hdcp message Suraj Kandpal
2024-01-31 19:39 ` [PATCH 08/10] drm/i915/hdcp: Extract hdcp structure from correct connector Suraj Kandpal
2024-02-02  5:17   ` Nautiyal, Ankit K
2024-01-31 19:39 ` [PATCH 09/10] drm/i915/hdcp: Allocate stream id after HDCP AKE stage Suraj Kandpal
2024-02-02  5:28   ` Nautiyal, Ankit K
2024-01-31 19:39 ` [PATCH 10/10] drm/i915/hdcp: Read Rxcaps for robustibility Suraj Kandpal
2024-02-01 18:03 ` ✗ Fi.CI.SPARSE: warning for HDCP Type1 MST fixes Patchwork
2024-02-02 12:26 ` ✗ Fi.CI.BAT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-01-31 19:32 [PATCH 00/10] " Suraj Kandpal
2024-01-31 19:32 ` [PATCH 02/10] drm/i915/hdcp: Move source hdcp2 checks into its own function Suraj Kandpal

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=20240131193929.938748-3-suraj.kandpal@intel.com \
    --to=suraj.kandpal@intel.com \
    --cc=intel-gfx@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.