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@ffwll.ch, seanpaul@chromium.org, tomas.winkler@intel.com,
	alexander.usyskin@intel.com, uma.shankar@intel.com
Subject: [PATCH v6 26/35] misc/mei/hdcp: Verify Receiver Cert and prepare km
Date: Sat, 14 Jul 2018 08:45:08 +0530	[thread overview]
Message-ID: <1531538117-1606-27-git-send-email-ramalingam.c@intel.com> (raw)
In-Reply-To: <1531538117-1606-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:
  No change.

Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
---
 drivers/misc/mei/hdcp/mei_hdcp.c | 85 +++++++++++++++++++++++++++++++++++++++-
 1 file changed, 84 insertions(+), 1 deletion(-)

diff --git a/drivers/misc/mei/hdcp/mei_hdcp.c b/drivers/misc/mei/hdcp/mei_hdcp.c
index 44b1aac03ff0..7d35066f21e2 100644
--- a/drivers/misc/mei/hdcp/mei_hdcp.c
+++ b/drivers/misc/mei/hdcp/mei_hdcp.c
@@ -105,10 +105,93 @@ static int mei_initiate_hdcp2_session(struct mei_cl_device *cldev,
 	return 0;
 }
 
+/*
+ * mei_verify_receiver_cert_prepare_km:
+ *	Function to verify the Receiver Certificate AKE_Send_Cert
+ *	and prepare AKE_Stored_Km or AKE_No_Stored_Km
+ *
+ * cldev		: Pointer for mei client device
+ * data			: Intel HW specific Data
+ * rx_cert		: Pointer for AKE_Send_Cert
+ * km_stored		: Pointer for pairing status flag
+ * ek_pub_km		: Pointer for output msg
+ * msg_sz		: Pointer for size of AKE_XXXXX_Km
+ *
+ * Returns 0 on Success, <0 on Failure
+ */
+static int
+mei_verify_receiver_cert_prepare_km(struct mei_cl_device *cldev,
+				    struct mei_hdcp_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 device *dev;
+	ssize_t byte;
+
+	if (!data || !rx_cert || !km_stored || !ek_pub_km || !msg_sz)
+		return -EINVAL;
+
+	dev = &cldev->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 = data->port;
+
+	memcpy(&verify_rxcert_in.cert_rx, &rx_cert->cert_rx,
+	       sizeof(rx_cert->cert_rx));
+	memcpy(verify_rxcert_in.r_rx, &rx_cert->r_rx, sizeof(rx_cert->r_rx));
+	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;
+}
+
 struct i915_hdcp_component_ops mei_hdcp_component_ops = {
 	.owner					= THIS_MODULE,
 	.initiate_hdcp2_session			= mei_initiate_hdcp2_session,
-	.verify_receiver_cert_prepare_km	= NULL,
+	.verify_receiver_cert_prepare_km	=
+					mei_verify_receiver_cert_prepare_km,
 	.verify_hprime				= NULL,
 	.store_pairing_info			= NULL,
 	.initiate_locality_check		= NULL,
-- 
2.7.4

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-07-14  3:15 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-14  3:14 [PATCH v6 00/35] drm/i915: Implement HDCP2.2 Ramalingam C
2018-07-14  3:14 ` [PATCH v6 01/35] drm: hdcp2.2 authentication msg definitions Ramalingam C
2018-07-31  6:21   ` Shankar, Uma
2018-08-01 11:14     ` Ramalingam C
2018-07-14  3:14 ` [PATCH v6 02/35] drm: HDMI and DP specific HDCP2.2 defines Ramalingam C
2018-07-31  8:25   ` Shankar, Uma
2018-08-01 11:34     ` Ramalingam C
2018-07-14  3:14 ` [PATCH v6 03/35] mei: bus: whitelist hdcp client Ramalingam C
2018-07-14  3:14 ` [PATCH v6 04/35] linux/mei: Header for mei_hdcp driver interface Ramalingam C
2018-07-31  8:39   ` Shankar, Uma
2018-07-14  3:14 ` [PATCH v6 05/35] drm/i915: wrapping all hdcp var into intel_hdcp Ramalingam C
2018-07-31  8:53   ` Shankar, Uma
2018-07-14  3:14 ` [PATCH v6 06/35] drm/i915: Define Intel HDCP2.2 registers Ramalingam C
2018-07-31  8:59   ` Shankar, Uma
2018-07-14  3:14 ` [PATCH v6 07/35] component: alloc component_match without any comp to match Ramalingam C
2018-07-14  3:14 ` [PATCH v6 08/35] drm/i915: component master at i915 driver load Ramalingam C
2018-07-14  3:14 ` [PATCH v6 09/35] drm/i915: Initialize HDCP2.2 and its MEI interface Ramalingam C
2018-07-17  1:29   ` kbuild test robot
2018-07-31 19:41   ` Shankar, Uma
2018-08-01 11:42     ` Ramalingam C
2018-07-14  3:14 ` [PATCH v6 10/35] drm/i915: Pullout the bksv read and validation Ramalingam C
2018-07-14  3:14 ` [PATCH v6 11/35] drm/i915: Enable and Disable of HDCP2.2 Ramalingam C
2018-07-31 20:49   ` Shankar, Uma
2018-07-14  3:14 ` [PATCH v6 12/35] drm/i915: Implement HDCP2.2 receiver authentication Ramalingam C
2018-08-01  9:41   ` Shankar, Uma
2018-08-30  6:34     ` Ramalingam C
2018-07-14  3:14 ` [PATCH v6 13/35] drm/i915: Implement HDCP2.2 repeater authentication Ramalingam C
2018-08-01 10:30   ` Shankar, Uma
2018-08-30  6:49     ` Ramalingam C
2018-07-14  3:14 ` [PATCH v6 14/35] drm/i915: Implement HDCP2.2 link integrity check Ramalingam C
2018-08-01 10:45   ` Shankar, Uma
2018-08-30  6:57     ` Ramalingam C
2018-07-14  3:14 ` [PATCH v6 15/35] drm/i915: Handle HDCP2.2 downstream topology change Ramalingam C
2018-07-14  3:14 ` [PATCH v6 16/35] drm/i915: hdcp_check_link only on CP_IRQ Ramalingam C
2018-07-14  3:14 ` [PATCH v6 17/35] drm/i915: Check HDCP 1.4 and 2.2 link " Ramalingam C
2018-08-01 11:02   ` Shankar, Uma
2018-08-30  7:24     ` Ramalingam C
2018-07-14  3:15 ` [PATCH v6 18/35] drm/i915: Implement the HDCP2.2 support for DP Ramalingam C
2018-08-01 11:31   ` Shankar, Uma
2018-07-14  3:15 ` [PATCH v6 19/35] drm/i915: Implement the HDCP2.2 support for HDMI Ramalingam C
2018-08-01 11:38   ` Shankar, Uma
2018-07-14  3:15 ` [PATCH v6 20/35] drm/i915: Add HDCP2.2 support for DP connectors Ramalingam C
2018-07-14  3:15 ` [PATCH v6 21/35] drm/i915: Add HDCP2.2 support for HDMI connectors Ramalingam C
2018-07-14  3:15 ` [PATCH v6 22/35] misc/mei/hdcp: Client driver for HDCP application Ramalingam C
2018-07-14  3:15 ` [PATCH v6 23/35] misc/mei/hdcp: Component framework for I915 Interface Ramalingam C
2018-08-01 13:06   ` Shankar, Uma
2018-07-14  3:15 ` [PATCH v6 24/35] misc/mei/hdcp: Define ME FW interface for HDCP2.2 Ramalingam C
2018-07-14  3:15 ` [PATCH v6 25/35] misc/mei/hdcp: Initiate Wired HDCP2.2 Tx Session Ramalingam C
2018-08-01 13:13   ` Shankar, Uma
2018-07-14  3:15 ` Ramalingam C [this message]
2018-08-01 13:18   ` [PATCH v6 26/35] misc/mei/hdcp: Verify Receiver Cert and prepare km Shankar, Uma
2018-07-14  3:15 ` [PATCH v6 27/35] misc/mei/hdcp: Verify H_prime Ramalingam C
2018-08-01 13:21   ` Shankar, Uma
2018-07-14  3:15 ` [PATCH v6 28/35] misc/mei/hdcp: Store the HDCP Pairing info Ramalingam C
2018-08-01 13:23   ` Shankar, Uma
2018-07-14  3:15 ` [PATCH v6 29/35] misc/mei/hdcp: Initiate Locality check Ramalingam C
2018-08-01 13:24   ` Shankar, Uma
2018-07-14  3:15 ` [PATCH v6 30/35] misc/mei/hdcp: Verify L_prime Ramalingam C
2018-08-01 13:26   ` Shankar, Uma
2018-07-14  3:15 ` [PATCH v6 31/35] misc/mei/hdcp: Prepare Session Key Ramalingam C
2018-08-01 13:29   ` Shankar, Uma
2018-07-14  3:15 ` [PATCH v6 32/35] misc/mei/hdcp: Repeater topology verification and ack Ramalingam C
2018-08-01 13:31   ` Shankar, Uma
2018-07-14  3:15 ` [PATCH v6 33/35] misc/mei/hdcp: Verify M_prime Ramalingam C
2018-08-01 13:33   ` Shankar, Uma
2018-07-14  3:15 ` [PATCH v6 34/35] misc/mei/hdcp: Enabling the HDCP authentication Ramalingam C
2018-08-01 13:36   ` Shankar, Uma
2018-07-14  3:15 ` [PATCH v6 35/35] misc/mei/hdcp: Closing wired HDCP2.2 Tx Session Ramalingam C
2018-08-01 13:38   ` Shankar, Uma
2018-07-14  3:39 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Implement HDCP2.2 (rev8) Patchwork
2018-07-14  3:49 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-07-14  3:55 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-07-30  9:09 ` [PATCH v6 00/35] drm/i915: Implement HDCP2.2 Shankar, Uma

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=1531538117-1606-27-git-send-email-ramalingam.c@intel.com \
    --to=ramalingam.c@intel.com \
    --cc=alexander.usyskin@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=seanpaul@chromium.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.