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 25/33] misc/mei/hdcp: Initiate Locality check
Date: Sat, 16 Feb 2019 23:07:12 +0530 [thread overview]
Message-ID: <1550338640-17470-26-git-send-email-ramalingam.c@intel.com> (raw)
In-Reply-To: <1550338640-17470-1-git-send-email-ramalingam.c@intel.com>
Requests ME to start the second stage of HDCP2.2 authentication,
called Locality Check.
On Success, ME FW will provide LC_Init message to send to hdcp sink.
v2: Rebased.
v3:
cldev is passed as first parameter [Tomas]
Redundant comments and cast are removed [Tomas]
v4:
%zd used 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]
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 | 57 +++++++++++++++++++++++++++++++++++++++-
1 file changed, 56 insertions(+), 1 deletion(-)
diff --git a/drivers/misc/mei/hdcp/mei_hdcp.c b/drivers/misc/mei/hdcp/mei_hdcp.c
index 1f5514244716..29ef61fd21d2 100644
--- a/drivers/misc/mei/hdcp/mei_hdcp.c
+++ b/drivers/misc/mei/hdcp/mei_hdcp.c
@@ -296,6 +296,61 @@ mei_hdcp_store_pairing_info(struct device *dev, struct hdcp_port_data *data,
return 0;
}
+/**
+ * mei_hdcp_initiate_locality_check() - Prepare LC_Init
+ * @dev: device corresponding to the mei_cl_device
+ * @data: Intel HW specific hdcp data
+ * @lc_init_data: LC_Init msg output
+ *
+ * Return: 0 on Success, <0 on Failure
+ */
+static int
+mei_hdcp_initiate_locality_check(struct device *dev,
+ struct hdcp_port_data *data,
+ struct hdcp2_lc_init *lc_init_data)
+{
+ struct wired_cmd_init_locality_check_in lc_init_in = { { 0 } };
+ struct wired_cmd_init_locality_check_out lc_init_out = { { 0 } };
+ struct mei_cl_device *cldev;
+ ssize_t byte;
+
+ if (!dev || !data || !lc_init_data)
+ return -EINVAL;
+
+ cldev = to_mei_cl_device(dev);
+
+ lc_init_in.header.api_version = HDCP_API_VERSION;
+ lc_init_in.header.command_id = WIRED_INIT_LOCALITY_CHECK;
+ lc_init_in.header.status = ME_HDCP_STATUS_SUCCESS;
+ lc_init_in.header.buffer_len = WIRED_CMD_BUF_LEN_INIT_LOCALITY_CHECK_IN;
+
+ lc_init_in.port.integrated_port_type = data->port_type;
+ lc_init_in.port.physical_port = mei_get_ddi_index(data->port);
+
+ byte = mei_cldev_send(cldev, (u8 *)&lc_init_in, sizeof(lc_init_in));
+ if (byte < 0) {
+ dev_dbg(dev, "mei_cldev_send failed. %zd\n", byte);
+ return byte;
+ }
+
+ byte = mei_cldev_recv(cldev, (u8 *)&lc_init_out, sizeof(lc_init_out));
+ if (byte < 0) {
+ dev_dbg(dev, "mei_cldev_recv failed. %zd\n", byte);
+ return byte;
+ }
+
+ if (lc_init_out.header.status != ME_HDCP_STATUS_SUCCESS) {
+ dev_dbg(dev, "ME cmd 0x%08X Failed. status: 0x%X\n",
+ WIRED_INIT_LOCALITY_CHECK, lc_init_out.header.status);
+ return -EIO;
+ }
+
+ lc_init_data->msg_id = HDCP_2_2_LC_INIT;
+ memcpy(lc_init_data->r_n, lc_init_out.r_n, HDCP_2_2_RN_LEN);
+
+ return 0;
+}
+
static __attribute__((unused))
struct i915_hdcp_component_ops mei_hdcp_ops = {
.owner = THIS_MODULE,
@@ -304,7 +359,7 @@ struct i915_hdcp_component_ops mei_hdcp_ops = {
mei_hdcp_verify_receiver_cert_prepare_km,
.verify_hprime = mei_hdcp_verify_hprime,
.store_pairing_info = mei_hdcp_store_pairing_info,
- .initiate_locality_check = NULL,
+ .initiate_locality_check = mei_hdcp_initiate_locality_check,
.verify_lprime = NULL,
.get_session_key = NULL,
.repeater_check_flow_prepare_ack = NULL,
--
2.7.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-02-16 17:37 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 17:36 [PATCH v14 00/33] drm/i915: Implement HDCP2.2 Ramalingam C
2019-02-16 17:36 ` [PATCH v14 01/33] drm/i915: Gathering the HDCP1.4 routines together Ramalingam C
2019-02-16 17:36 ` [PATCH v14 02/33] drm/audio: declaration of struct device Ramalingam C
2019-02-16 17:36 ` [PATCH v14 03/33] drm/i915: Initialize HDCP2.2 Ramalingam C via dri-devel
2019-02-16 17:36 ` [PATCH v14 04/33] drm/i915: MEI interface implementation Ramalingam C via dri-devel
2019-02-20 19:39 ` Daniel Vetter
2019-02-21 4:07 ` C, Ramalingam
2019-02-16 17:36 ` [PATCH v14 05/33] drm/i915: hdcp1.4 CP_IRQ handling and SW encryption tracking Ramalingam C
2019-02-16 17:36 ` [PATCH v14 06/33] drm/i915: Enable and Disable of HDCP2.2 Ramalingam C
2019-02-16 17:36 ` [PATCH v14 07/33] drm/i915: Implement HDCP2.2 receiver authentication Ramalingam C
2019-02-16 17:36 ` [PATCH v14 08/33] drm/i915: Implement HDCP2.2 repeater authentication Ramalingam C via dri-devel
2019-02-16 17:36 ` [PATCH v14 09/33] drm: HDCP2.2 link check period Ramalingam C
2019-02-16 17:36 ` [PATCH v14 10/33] drm/i915: Implement HDCP2.2 link integrity check Ramalingam C
2019-02-16 17:36 ` [PATCH v14 11/33] drm/i915: Handle HDCP2.2 downstream topology change Ramalingam C via dri-devel
2019-02-16 17:36 ` [PATCH v14 12/33] drm: removing the DP Errata msg and its msg id Ramalingam C
2019-02-16 17:37 ` [PATCH v14 13/33] drm/i915: Implement the HDCP2.2 support for DP Ramalingam C
2019-08-15 8:43 ` Jani Nikula
2019-08-19 15:06 ` Ramalingam C
2019-02-16 17:37 ` [PATCH v14 14/33] drm/i915: Implement the HDCP2.2 support for HDMI Ramalingam C
2019-02-16 17:37 ` [PATCH v14 15/33] drm/i915: CP_IRQ handling for DP HDCP2.2 msgs Ramalingam C via dri-devel
2019-02-16 17:37 ` [PATCH v14 16/33] drm/i915: Fix KBL HDCP2.2 encrypt status signalling Ramalingam C
2019-02-20 19:49 ` Daniel Vetter
2019-02-16 17:37 ` [PATCH v14 17/33] mei: bus: whitelist hdcp client Ramalingam C
2019-02-16 17:37 ` [PATCH v14 18/33] mei: bus: export to_mei_cl_device for mei client device drivers Ramalingam C
2019-02-16 17:37 ` [PATCH v14 19/33] misc/mei/hdcp: Client driver for HDCP application Ramalingam C
2019-02-21 13:55 ` Winkler, Tomas
2019-02-16 17:37 ` [PATCH v14 20/33] misc/mei/hdcp: Define ME FW interface for HDCP2.2 Ramalingam C via dri-devel
2019-02-21 12:42 ` Winkler, Tomas
2019-02-16 17:37 ` [PATCH v14 21/33] misc/mei/hdcp: Initiate Wired HDCP2.2 Tx Session Ramalingam C
2019-02-21 13:30 ` Winkler, Tomas
2019-02-16 17:37 ` [PATCH v14 22/33] misc/mei/hdcp: Verify Receiver Cert and prepare km Ramalingam C
2019-02-21 13:39 ` Winkler, Tomas
2019-02-16 17:37 ` [PATCH v14 23/33] misc/mei/hdcp: Verify H_prime Ramalingam C
2019-02-21 13:32 ` Winkler, Tomas
2019-02-21 13:33 ` Winkler, Tomas
2019-02-16 17:37 ` [PATCH v14 24/33] misc/mei/hdcp: Store the HDCP Pairing info Ramalingam C
2019-02-21 13:46 ` Winkler, Tomas
2019-02-16 17:37 ` Ramalingam C [this message]
2019-02-21 13:40 ` [PATCH v14 25/33] misc/mei/hdcp: Initiate Locality check Winkler, Tomas
2019-02-16 17:37 ` [PATCH v14 26/33] misc/mei/hdcp: Verify L_prime Ramalingam C
2019-02-21 13:42 ` Winkler, Tomas
2019-02-16 17:37 ` [PATCH v14 27/33] misc/mei/hdcp: Prepare Session Key Ramalingam C
2019-02-21 14:24 ` Winkler, Tomas
2019-02-16 17:37 ` [PATCH v14 28/33] misc/mei/hdcp: Repeater topology verification and ack Ramalingam C via dri-devel
2019-02-21 14:16 ` Winkler, Tomas
2019-02-16 17:37 ` [PATCH v14 29/33] misc/mei/hdcp: Verify M_prime Ramalingam C via dri-devel
2019-02-21 13:44 ` Winkler, Tomas
2019-02-16 17:37 ` [PATCH v14 30/33] misc/mei/hdcp: Enabling the HDCP authentication Ramalingam C
2019-02-21 14:25 ` Winkler, Tomas
2019-02-16 17:37 ` [PATCH v14 31/33] misc/mei/hdcp: Closing wired HDCP2.2 Tx Session Ramalingam C
2019-02-21 14:25 ` Winkler, Tomas
2019-02-16 17:37 ` [PATCH v14 32/33] misc/mei/hdcp: Component framework for I915 Interface Ramalingam C
2019-02-21 12:15 ` Winkler, Tomas
2019-02-16 17:37 ` [PATCH v14 33/33] FOR_TEST_ONLY: i915/Kconfig: Select mei_hdcp by I915 Ramalingam C via dri-devel
2019-02-16 18:18 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Implement HDCP2.2 Patchwork
2019-02-16 18:28 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-02-16 18:45 ` ✓ Fi.CI.BAT: success " Patchwork
2019-02-16 20:49 ` ✓ Fi.CI.IGT: " 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=1550338640-17470-26-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox