All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramalingam C <ramalingam.c@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	daniel.vetter@ffwll.ch, tomas.winkler@intel.com,
	uma.shankar@intel.com
Subject: [PATCH v14 24/35] misc/mei/hdcp: Verify Receiver Cert and prepare km
Date: Fri, 15 Feb 2019 14:05:19 +0530	[thread overview]
Message-ID: <1550219730-17734-25-git-send-email-ramalingam.c@intel.com> (raw)
In-Reply-To: <1550219730-17734-1-git-send-email-ramalingam.c@intel.com>

Requests for verification for receiver certification and also the
preparation for next AKE auth message with km.

On Success ME FW validate the HDCP2.2 receivers certificate and do the
revocation check on the receiver ID. AKE_Stored_Km will be prepared if
the receiver is already paired, else AKE_No_Stored_Km will be prepared.

Here AKE_Stored_Km and AKE_No_Stored_Km are HDCP2.2 protocol msgs.

v2: Rebased.
v3:
  cldev is passed as first parameter [Tomas]
  Redundant comments and cast are removed [Tomas]
v4:
  %zd is used for ssize_t [Alexander]
  %s/return -1/return -EIO [Alexander]
v5: Rebased.
v6:
  Collected the Rb-ed by.
  Rebasing.
v7:
  Adjust to the new mei interface.
  Fix for Kdoc.
v8:
  K-Doc Addition. [Tomas]
  memcpy for const length.
v9:
  renamed func as mei_hdcp_* [Tomas]
  Inline function is defined for DDI index [Tomas]
v10:
  Fixed the conversion of u8 to bool [Tomas]
  K-Doc fix [Tomas]

Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
Reviewed-by: Uma Shankar <uma.shankar@intel.com>
Acked-by: Tomas Winkler <tomas.winkler@intel.com>
---
 drivers/misc/mei/hdcp/mei_hdcp.c | 83 +++++++++++++++++++++++++++++++++++++++-
 1 file changed, 82 insertions(+), 1 deletion(-)

diff --git a/drivers/misc/mei/hdcp/mei_hdcp.c b/drivers/misc/mei/hdcp/mei_hdcp.c
index 952bae79dd02..922c6a76bb9f 100644
--- a/drivers/misc/mei/hdcp/mei_hdcp.c
+++ b/drivers/misc/mei/hdcp/mei_hdcp.c
@@ -102,11 +102,92 @@ mei_hdcp_initiate_session(struct device *dev, struct hdcp_port_data *data,
 	return 0;
 }
 
+/**
+ * mei_hdcp_verify_receiver_cert_prepare_km() - Verify the Receiver Certificate
+ * AKE_Send_Cert and prepare AKE_Stored_Km/AKE_No_Stored_Km
+ * @dev: device corresponding to the mei_cl_device
+ * @data: Intel HW specific hdcp data
+ * @rx_cert: AKE_Send_Cert for verification
+ * @km_stored: Pairing status flag output
+ * @ek_pub_km: AKE_Stored_Km/AKE_No_Stored_Km output msg
+ * @msg_sz : size of AKE_XXXXX_Km output msg
+ *
+ * Return: 0 on Success, <0 on Failure
+ */
+static int
+mei_hdcp_verify_receiver_cert_prepare_km(struct device *dev,
+					 struct hdcp_port_data *data,
+					 struct hdcp2_ake_send_cert *rx_cert,
+					 bool *km_stored,
+					 struct hdcp2_ake_no_stored_km
+								*ek_pub_km,
+					 size_t *msg_sz)
+{
+	struct wired_cmd_verify_receiver_cert_in verify_rxcert_in = { { 0 } };
+	struct wired_cmd_verify_receiver_cert_out verify_rxcert_out = { { 0 } };
+	struct mei_cl_device *cldev;
+	ssize_t byte;
+
+	if (!dev || !data || !rx_cert || !km_stored || !ek_pub_km || !msg_sz)
+		return -EINVAL;
+
+	cldev = to_mei_cl_device(dev);
+
+	verify_rxcert_in.header.api_version = HDCP_API_VERSION;
+	verify_rxcert_in.header.command_id = WIRED_VERIFY_RECEIVER_CERT;
+	verify_rxcert_in.header.status = ME_HDCP_STATUS_SUCCESS;
+	verify_rxcert_in.header.buffer_len =
+				WIRED_CMD_BUF_LEN_VERIFY_RECEIVER_CERT_IN;
+
+	verify_rxcert_in.port.integrated_port_type = data->port_type;
+	verify_rxcert_in.port.physical_port = mei_get_ddi_index(data->port);
+
+	verify_rxcert_in.cert_rx = rx_cert->cert_rx;
+	memcpy(verify_rxcert_in.r_rx, &rx_cert->r_rx, HDCP_2_2_RRX_LEN);
+	memcpy(verify_rxcert_in.rx_caps, rx_cert->rx_caps, HDCP_2_2_RXCAPS_LEN);
+
+	byte = mei_cldev_send(cldev, (u8 *)&verify_rxcert_in,
+			      sizeof(verify_rxcert_in));
+	if (byte < 0) {
+		dev_dbg(dev, "mei_cldev_send failed: %zd\n", byte);
+		return byte;
+	}
+
+	byte = mei_cldev_recv(cldev, (u8 *)&verify_rxcert_out,
+			      sizeof(verify_rxcert_out));
+	if (byte < 0) {
+		dev_dbg(dev, "mei_cldev_recv failed: %zd\n", byte);
+		return byte;
+	}
+
+	if (verify_rxcert_out.header.status != ME_HDCP_STATUS_SUCCESS) {
+		dev_dbg(dev, "ME cmd 0x%08X Failed. Status: 0x%X\n",
+			WIRED_VERIFY_RECEIVER_CERT,
+			verify_rxcert_out.header.status);
+		return -EIO;
+	}
+
+	*km_stored = !!verify_rxcert_out.km_stored;
+	if (verify_rxcert_out.km_stored) {
+		ek_pub_km->msg_id = HDCP_2_2_AKE_STORED_KM;
+		*msg_sz = sizeof(struct hdcp2_ake_stored_km);
+	} else {
+		ek_pub_km->msg_id = HDCP_2_2_AKE_NO_STORED_KM;
+		*msg_sz = sizeof(struct hdcp2_ake_no_stored_km);
+	}
+
+	memcpy(ek_pub_km->e_kpub_km, &verify_rxcert_out.ekm_buff,
+	       sizeof(verify_rxcert_out.ekm_buff));
+
+	return 0;
+}
+
 static __attribute__((unused))
 struct i915_hdcp_component_ops mei_hdcp_ops = {
 	.owner = THIS_MODULE,
 	.initiate_hdcp2_session = mei_hdcp_initiate_session,
-	.verify_receiver_cert_prepare_km = NULL,
+	.verify_receiver_cert_prepare_km =
+				mei_hdcp_verify_receiver_cert_prepare_km,
 	.verify_hprime = NULL,
 	.store_pairing_info = NULL,
 	.initiate_locality_check = NULL,
-- 
2.7.4

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-02-15  8:35 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15  8:34 [PATCH v14 00/35] drm/i915: Implement HDCP2.2 Ramalingam C
2019-02-15  8:34 ` [PATCH v14 01/35] drm/i915: Gathering the HDCP1.4 routines together Ramalingam C
2019-02-15  8:34 ` [PATCH v14 02/35] drm: enum port definition is moved into i915_drm.h Ramalingam C
2019-02-15 17:47   ` Daniel Vetter
2019-02-15  8:34 ` [PATCH v14 03/35] drm: header for i915 - MEI_HDCP interface Ramalingam C
2019-02-15 17:47   ` Daniel Vetter
2019-02-15  8:34 ` [PATCH v14 04/35] drm/i915: Initialize HDCP2.2 Ramalingam C
2019-02-15  8:35 ` [PATCH v14 05/35] drm/i915: MEI interface definition Ramalingam C via dri-devel
2019-02-15 17:53   ` Daniel Vetter
2019-02-15  8:35 ` [PATCH v14 06/35] drm/i915: hdcp1.4 CP_IRQ handling and SW encryption tracking Ramalingam C
2019-02-15  8:35 ` [PATCH v14 07/35] drm/i915: Enable and Disable of HDCP2.2 Ramalingam C
2019-02-15  8:35 ` [PATCH v14 08/35] drm/i915: Implement HDCP2.2 receiver authentication Ramalingam C
2019-02-15  8:35 ` [PATCH v14 09/35] drm: helper functions for hdcp2 seq_num to from u32 Ramalingam C
2019-02-15 17:56   ` Daniel Vetter
2019-02-15  8:35 ` [PATCH v14 10/35] drm/i915: Implement HDCP2.2 repeater authentication Ramalingam C
2019-02-15  8:35 ` [PATCH v14 11/35] drm: HDCP2.2 link check period Ramalingam C
2019-02-15  8:35 ` [PATCH v14 12/35] drm/i915: Implement HDCP2.2 link integrity check Ramalingam C
2019-02-15  8:35 ` [PATCH v14 13/35] drm/i915: Handle HDCP2.2 downstream topology change Ramalingam C
2019-02-15  8:35 ` [PATCH v14 14/35] drm: removing the DP Errata msg and its msg id Ramalingam C
2019-02-15  8:35 ` [PATCH v14 15/35] drm/i915: Implement the HDCP2.2 support for DP Ramalingam C via dri-devel
2019-02-15  8:35 ` [PATCH v14 16/35] drm/i915: Implement the HDCP2.2 support for HDMI Ramalingam C
2019-02-15  8:35 ` [PATCH v14 17/35] drm/i915: CP_IRQ handling for DP HDCP2.2 msgs Ramalingam C
2019-02-15  8:35 ` [PATCH v14 18/35] drm/i915: Fix KBL HDCP2.2 encrypt status signalling Ramalingam C via dri-devel
2019-02-15  8:35 ` [PATCH v14 19/35] mei: bus: whitelist hdcp client Ramalingam C
2019-02-15  8:35 ` [PATCH v14 20/35] mei: bus: export to_mei_cl_device for mei client device drivers Ramalingam C
2019-02-15  8:35 ` [PATCH v14 21/35] misc/mei/hdcp: Client driver for HDCP application Ramalingam C
2019-02-15  8:35 ` [PATCH v14 22/35] misc/mei/hdcp: Define ME FW interface for HDCP2.2 Ramalingam C
2019-02-15  8:35 ` [PATCH v14 23/35] misc/mei/hdcp: Initiate Wired HDCP2.2 Tx Session Ramalingam C
2019-02-15  8:35 ` Ramalingam C [this message]
2019-02-15  8:35 ` [PATCH v14 25/35] misc/mei/hdcp: Verify H_prime Ramalingam C
2019-02-15  8:35 ` [PATCH v14 26/35] misc/mei/hdcp: Store the HDCP Pairing info Ramalingam C via dri-devel
2019-02-15  8:35 ` [PATCH v14 27/35] misc/mei/hdcp: Initiate Locality check Ramalingam C
2019-02-15  8:35 ` [PATCH v14 28/35] misc/mei/hdcp: Verify L_prime Ramalingam C
2019-02-15  8:35 ` [PATCH v14 29/35] misc/mei/hdcp: Prepare Session Key Ramalingam C
2019-02-15  8:35 ` [PATCH v14 30/35] misc/mei/hdcp: Repeater topology verification and ack Ramalingam C
2019-02-15  8:35 ` [PATCH v14 31/35] misc/mei/hdcp: Verify M_prime Ramalingam C
2019-02-15  8:35 ` [PATCH v14 32/35] misc/mei/hdcp: Enabling the HDCP authentication Ramalingam C via dri-devel
2019-02-15  8:35 ` [PATCH v14 33/35] misc/mei/hdcp: Closing wired HDCP2.2 Tx Session Ramalingam C
2019-02-15  8:35 ` [PATCH v14 34/35] misc/mei/hdcp: Component framework for I915 Interface Ramalingam C
2019-02-15  8:35 ` [PATCH v14 35/35] FOR_TEST_ONLY: i915/Kconfig: Select mei_hdcp by I915 Ramalingam C
2019-02-16 20:46 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Implement HDCP2.2 Patchwork
2019-02-16 20:56 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-02-16 21:07 ` ✗ 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=1550219730-17734-25-git-send-email-ramalingam.c@intel.com \
    --to=ramalingam.c@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tomas.winkler@intel.com \
    --cc=uma.shankar@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 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.