From: Ramalingam C via dri-devel <dri-devel@lists.freedesktop.org>
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 26/35] misc/mei/hdcp: Store the HDCP Pairing info
Date: Fri, 15 Feb 2019 14:05:21 +0530 [thread overview]
Message-ID: <1550219730-17734-27-git-send-email-ramalingam.c@intel.com> (raw)
In-Reply-To: <1550219730-17734-1-git-send-email-ramalingam.c@intel.com>
Provides Pairing info to ME to store.
Pairing is a process to fast track the subsequent authentication
with the same HDCP sink.
On Success, received HDCP pairing info is stored in non-volatile
memory of ME.
v2: Rebased.
v3:
cldev is passed as first parameter [Tomas]
Redundant comments and cast are removed [Tomas]
v4:
%zd for ssize_t [Alexander]
%s/return -1/return -EIO [Alexander]
Style fixed [Uma]
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:
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 | 60 +++++++++++++++++++++++++++++++++++++++-
1 file changed, 59 insertions(+), 1 deletion(-)
diff --git a/drivers/misc/mei/hdcp/mei_hdcp.c b/drivers/misc/mei/hdcp/mei_hdcp.c
index 0a4087a2efd5..1f5514244716 100644
--- a/drivers/misc/mei/hdcp/mei_hdcp.c
+++ b/drivers/misc/mei/hdcp/mei_hdcp.c
@@ -238,6 +238,64 @@ mei_hdcp_verify_hprime(struct device *dev, struct hdcp_port_data *data,
return 0;
}
+/**
+ * mei_hdcp_store_pairing_info() - Store pairing info received at ME FW
+ * @dev: device corresponding to the mei_cl_device
+ * @data: Intel HW specific hdcp data
+ * @pairing_info: AKE_Send_Pairing_Info msg input to ME FW
+ *
+ * Return: 0 on Success, <0 on Failure
+ */
+static int
+mei_hdcp_store_pairing_info(struct device *dev, struct hdcp_port_data *data,
+ struct hdcp2_ake_send_pairing_info *pairing_info)
+{
+ struct wired_cmd_ake_send_pairing_info_in pairing_info_in = { { 0 } };
+ struct wired_cmd_ake_send_pairing_info_out pairing_info_out = { { 0 } };
+ struct mei_cl_device *cldev;
+ ssize_t byte;
+
+ if (!dev || !data || !pairing_info)
+ return -EINVAL;
+
+ cldev = to_mei_cl_device(dev);
+
+ pairing_info_in.header.api_version = HDCP_API_VERSION;
+ pairing_info_in.header.command_id = WIRED_AKE_SEND_PAIRING_INFO;
+ pairing_info_in.header.status = ME_HDCP_STATUS_SUCCESS;
+ pairing_info_in.header.buffer_len =
+ WIRED_CMD_BUF_LEN_SEND_PAIRING_INFO_IN;
+
+ pairing_info_in.port.integrated_port_type = data->port_type;
+ pairing_info_in.port.physical_port = mei_get_ddi_index(data->port);
+
+ memcpy(pairing_info_in.e_kh_km, pairing_info->e_kh_km,
+ HDCP_2_2_E_KH_KM_LEN);
+
+ byte = mei_cldev_send(cldev, (u8 *)&pairing_info_in,
+ sizeof(pairing_info_in));
+ if (byte < 0) {
+ dev_dbg(dev, "mei_cldev_send failed. %zd\n", byte);
+ return byte;
+ }
+
+ byte = mei_cldev_recv(cldev, (u8 *)&pairing_info_out,
+ sizeof(pairing_info_out));
+ if (byte < 0) {
+ dev_dbg(dev, "mei_cldev_recv failed. %zd\n", byte);
+ return byte;
+ }
+
+ if (pairing_info_out.header.status != ME_HDCP_STATUS_SUCCESS) {
+ dev_dbg(dev, "ME cmd 0x%08X failed. Status: 0x%X\n",
+ WIRED_AKE_SEND_PAIRING_INFO,
+ pairing_info_out.header.status);
+ return -EIO;
+ }
+
+ return 0;
+}
+
static __attribute__((unused))
struct i915_hdcp_component_ops mei_hdcp_ops = {
.owner = THIS_MODULE,
@@ -245,7 +303,7 @@ struct i915_hdcp_component_ops mei_hdcp_ops = {
.verify_receiver_cert_prepare_km =
mei_hdcp_verify_receiver_cert_prepare_km,
.verify_hprime = mei_hdcp_verify_hprime,
- .store_pairing_info = NULL,
+ .store_pairing_info = mei_hdcp_store_pairing_info,
.initiate_locality_check = NULL,
.verify_lprime = NULL,
.get_session_key = NULL,
--
2.7.4
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev 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 ` [PATCH v14 24/35] misc/mei/hdcp: Verify Receiver Cert and prepare km Ramalingam C
2019-02-15 8:35 ` [PATCH v14 25/35] misc/mei/hdcp: Verify H_prime Ramalingam C
2019-02-15 8:35 ` Ramalingam C via dri-devel [this message]
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-27-git-send-email-ramalingam.c@intel.com \
--to=dri-devel@lists.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ramalingam.c@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox