public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "C, Ramalingam" <ramalingam.c@intel.com>
To: "Winkler, Tomas" <tomas.winkler@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH v10 25/40] misc/mei/hdcp: Initiate Wired HDCP2.2 Tx Session
Date: Tue, 5 Feb 2019 19:43:42 +0530	[thread overview]
Message-ID: <c6a12119-3537-2d58-80b4-0f4b623a9ef9@intel.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B9DA90C06@hasmsx108.ger.corp.intel.com>


Thanks Tomas.

On 2/5/2019 6:39 PM, Winkler, Tomas wrote:
>>> Request ME FW to start the HDCP2.2 session for an intel port.
>>> Prepares payloads for command WIRED_INITIATE_HDCP2_SESSION and sends
>> to
>>> ME FW.
>>>
>>> On Success, ME FW will start a HDCP2.2 session for the port and
>>> provides the content for HDCP2.2 AKE_Init message.
>>>
>>> v2: Rebased.
>>> v3:
>>>   cldev is add as a separate parameter [Tomas]
>>>   Redundant comment and typecast are removed [Tomas]
>>> v4:
>>>   %zd is used for size [Alexander]
>>>   %s/return -1/return -EIO [Alexander]
>>>   Spellings in commit msg is fixed [Uma]
>>> v5: Rebased.
>>> v6:
>>>   Collected the rb-ed by.
>>>   Realigning the patches in the series.
>>> v7:
>>>   Adjust to the new mei interface.
>>>   Fix for kdoc.
>>> v8:
>>>   K-Doc Addition.
>>>   memcpy for const length.
>>>
>>> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
>>> Reviewed-by: Uma Shankar <uma.shankar@intel.com>
>> Latest set look ok. You can keep the RB.
>>
>>> ---
>>> drivers/misc/mei/hdcp/mei_hdcp.c | 82
>>> ++++++++++++++++++++++++++++++++++++++++
>>> drivers/misc/mei/hdcp/mei_hdcp.h | 28 ++++++++++++++
>>> 2 files changed, 110 insertions(+)
>>>
>>> diff --git a/drivers/misc/mei/hdcp/mei_hdcp.c
>>> b/drivers/misc/mei/hdcp/mei_hdcp.c
>>> index ca5010ad7dd7..534d29c8ee86 100644
>>> --- a/drivers/misc/mei/hdcp/mei_hdcp.c
>>> +++ b/drivers/misc/mei/hdcp/mei_hdcp.c
>>> @@ -23,6 +23,88 @@
>>> #include <linux/slab.h>
>>> #include <linux/uuid.h>
>>> #include <linux/mei_cl_bus.h>
>>> +#include <drm/drm_connector.h>
>>> +#include <drm/i915_component.h>
>>> +#include <drm/i915_mei_hdcp_interface.h>
>>> +
>>> +#include "mei_hdcp.h"
>>> +
>>> +/**
>>> + * mei_initiate_hdcp2_session() - Initiate a Wired HDCP2.2 Tx Session
>>> +in ME FW
>>> + * @dev: device corresponding to the mei_cl_device
>>> + * @hdcp_data: Intel HW specific hdcp data
>>> + * @ake_data: AKE_Init msg output.
>>> + *
>>> + * Return:  0 on Success, <0 on Failure.
>>> + */
>>> +static int
>>> +mei_initiate_hdcp2_session(struct device *dev, struct hdcp_port_data *data,
>>> +			   struct hdcp2_ake_init *ake_data) {
>
> Breaking naming conventions : all functions should be prefixed with mei_hdcp_
>
> e.g. mei_hdcp_ initiate_session()
I will rename all the function name similarly.

--Ram
>
>>> +	struct wired_cmd_initiate_hdcp2_session_in session_init_in = { { 0 } };
>>> +	struct wired_cmd_initiate_hdcp2_session_out
>>> +						session_init_out = { { 0 } };
>>> +	struct mei_cl_device *cldev;
>>> +	ssize_t byte;
>>> +
>>> +	if (!dev || !data || !ake_data)
>>> +		return -EINVAL;
>>> +
>>> +	cldev = to_mei_cl_device(dev);
>>> +
>>> +	session_init_in.header.api_version = HDCP_API_VERSION;
>>> +	session_init_in.header.command_id =
>>> WIRED_INITIATE_HDCP2_SESSION;
>>> +	session_init_in.header.status = ME_HDCP_STATUS_SUCCESS;
>>> +	session_init_in.header.buffer_len =
>>> +
>>> 	WIRED_CMD_BUF_LEN_INITIATE_HDCP2_SESSION_IN;
>>> +
>>> +	session_init_in.port.integrated_port_type = data->port_type;
>>> +	session_init_in.port.physical_port = (u8)GET_MEI_DDI_INDEX(data-
>>>> port);
>>> +	session_init_in.protocol = data->protocol;
>>> +
>>> +	byte = mei_cldev_send(cldev, (u8 *)&session_init_in,
>>> +			      sizeof(session_init_in));
>>> +	if (byte < 0) {
>>> +		dev_dbg(dev, "mei_cldev_send failed. %zd\n", byte);
>>> +		return byte;
>>> +	}
>>> +
>>> +	byte = mei_cldev_recv(cldev, (u8 *)&session_init_out,
>>> +			      sizeof(session_init_out));
>>> +	if (byte < 0) {
>>> +		dev_dbg(dev, "mei_cldev_recv failed. %zd\n", byte);
>>> +		return byte;
>>> +	}
>>> +
>>> +	if (session_init_out.header.status != ME_HDCP_STATUS_SUCCESS) {
>>> +		dev_dbg(dev, "ME cmd 0x%08X Failed. Status: 0x%X\n",
>>> +			WIRED_INITIATE_HDCP2_SESSION,
>>> +			session_init_out.header.status);
>>> +		return -EIO;
>>> +	}
>>> +
>>> +	ake_data->msg_id = HDCP_2_2_AKE_INIT;
>>> +	ake_data->tx_caps = session_init_out.tx_caps;
>>> +	memcpy(ake_data->r_tx, session_init_out.r_tx, HDCP_2_2_RTX_LEN);
>>> +
>>> +	return 0;
>>> +}
>>> +
>>> +static __attribute__((unused))
>>> +struct i915_hdcp_component_ops mei_hdcp_ops = {
>>> +	.owner = THIS_MODULE,
>>> +	.initiate_hdcp2_session = mei_initiate_hdcp2_session,
>>> +	.verify_receiver_cert_prepare_km = NULL,
>>> +	.verify_hprime = NULL,
>>> +	.store_pairing_info = NULL,
>>> +	.initiate_locality_check = NULL,
>>> +	.verify_lprime = NULL,
>>> +	.get_session_key = NULL,
>>> +	.repeater_check_flow_prepare_ack = NULL,
>>> +	.verify_mprime = NULL,
>>> +	.enable_hdcp_authentication = NULL,
>>> +	.close_hdcp_session = NULL,
>>> +};
>>>
>>> static int mei_hdcp_probe(struct mei_cl_device *cldev,
>>> 			  const struct mei_cl_device_id *id) diff --git
>>> a/drivers/misc/mei/hdcp/mei_hdcp.h b/drivers/misc/mei/hdcp/mei_hdcp.h
>>> index 582a7e27ae29..f831db3cbd54 100644
>>> --- a/drivers/misc/mei/hdcp/mei_hdcp.h
>>> +++ b/drivers/misc/mei/hdcp/mei_hdcp.h
>>> @@ -363,4 +363,32 @@ struct wired_cmd_repeater_auth_stream_req_out {
>>> 	struct hdcp_port_id	port;
>>> } __packed;
>>>
>>> +enum mei_hdcp_ddi {
>>> +	MEI_DDI_INVALID_PORT = 0x0,
>>> +
>>> +	MEI_DDI_B = 1,
>>> +	MEI_DDI_C,
>>> +	MEI_DDI_D,
>>> +	MEI_DDI_E,
>>> +	MEI_DDI_F,
>>> +	MEI_DDI_A = 7,
>>> +	MEI_DDI_RANGE_END = MEI_DDI_A,
>>> +};
>>> +
>>> +enum i915_port {
> We've already reviewed. Move to i915 header or use mei_ prefix?
renaming it to mei_i915_port, like wise s/mei_hdcp_ddi/mei_fw_ddi to 
make more sense

--Ram
>>> +	PORT_NONE = -1,
>>> +
>>> +	PORT_A = 0,
>>> +	PORT_B,
>>> +	PORT_C,
>>> +	PORT_D,
>>> +	PORT_E,
>>> +	PORT_F,
>>> +	I915_MAX_PORTS,
>>> +};
>>> +
>>> +#define GET_MEI_DDI_INDEX(p) ({
>>> 	\
>>> +	enum i915_port __p = (enum i915_port)(p);			\
>>> +	__p == PORT_A ? MEI_DDI_A : (enum mei_hdcp_ddi)__p;
>> 	\
>>> +})
>>> #endif /* __MEI_HDCP_H__ */
>>> --
>>> 2.7.4

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

  reply	other threads:[~2019-02-05 14:13 UTC|newest]

Thread overview: 109+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31  6:59 [PATCH v10 00/40] drm/i915: Implement HDCP2.2 Ramalingam C
2019-01-31  6:59 ` [PATCH v10 01/40] components: multiple components for a device Ramalingam C
2019-01-31  7:50   ` Greg Kroah-Hartman
2019-01-31  8:00     ` Daniel Vetter
2019-01-31  8:12       ` Greg Kroah-Hartman
2019-01-31  8:39         ` Daniel Vetter
2019-02-06 16:45   ` [PATCH 1/3] component: Add documentation Daniel Vetter
2019-02-06 16:45     ` [PATCH 2/3] components: multiple components for a device Daniel Vetter
2019-02-06 22:57       ` Rafael J. Wysocki
2019-02-07 22:35         ` Daniel Vetter
2019-02-07 22:40         ` Daniel Vetter
2019-02-07 22:48           ` Rafael J. Wysocki
2019-02-06 16:45     ` [PATCH 3/3] drm/doc: document recommended component helper usage Daniel Vetter
2019-01-31  6:59 ` [PATCH v10 02/40] i915/snd_hdac: I915 subcomponent for the snd_hdac Ramalingam C
2019-02-04 15:00   ` Daniel Vetter
2019-02-04 15:09     ` Takashi Iwai
2019-01-31  6:59 ` [PATCH v10 03/40] drm/i915: Gathering the HDCP1.4 routines together Ramalingam C
2019-02-04 13:11   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 04/40] drm: header for i915 - MEI_HDCP interface Ramalingam C
2019-02-04 13:24   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 05/40] drm/i915: Initialize HDCP2.2 Ramalingam C
2019-02-04 13:29   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 06/40] drm/i915: MEI interface definition Ramalingam C
2019-01-31  8:17   ` Daniel Vetter
2019-01-31 13:39     ` C, Ramalingam
2019-01-31  6:59 ` [PATCH v10 07/40] drm/i915: hdcp1.4 CP_IRQ handling and SW encryption tracking Ramalingam C
2019-01-31  7:56   ` Daniel Vetter
2019-01-31 13:41     ` C, Ramalingam
2019-02-04 14:09   ` Shankar, Uma
2019-02-04 14:43     ` C, Ramalingam
2019-01-31  6:59 ` [PATCH v10 08/40] drm/i915: Enable and Disable of HDCP2.2 Ramalingam C
2019-02-04 14:17   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 09/40] drm/i915: Implement HDCP2.2 receiver authentication Ramalingam C
2019-02-04 14:20   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 10/40] drm: helper functions for hdcp2 seq_num to from u32 Ramalingam C
2019-02-04 14:20   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 11/40] drm/i915: Implement HDCP2.2 repeater authentication Ramalingam C
2019-02-04 14:21   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 12/40] drm: HDCP2.2 link check period Ramalingam C
2019-02-04 14:24   ` Shankar, Uma
2019-02-04 14:50     ` C, Ramalingam
2019-01-31  6:59 ` [PATCH v10 13/40] drm/i915: Implement HDCP2.2 link integrity check Ramalingam C
2019-02-04 14:28   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 14/40] drm/i915: Handle HDCP2.2 downstream topology change Ramalingam C
2019-02-04 14:31   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 15/40] drm: removing the DP Errata msg and its msg id Ramalingam C
2019-01-31  8:02   ` Daniel Vetter
2019-02-04 14:35   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 16/40] drm/i915: Implement the HDCP2.2 support for DP Ramalingam C
2019-02-04 16:02   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 17/40] drm/i915: Implement the HDCP2.2 support for HDMI Ramalingam C
2019-02-04 16:03   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 18/40] drm/i915: CP_IRQ handling for DP HDCP2.2 msgs Ramalingam C
2019-01-31  8:08   ` Daniel Vetter
2019-01-31 12:50     ` Daniel Vetter
2019-01-31  6:59 ` [PATCH v10 19/40] drm/i915: Add HDCP2.2 support for DP connectors Ramalingam C
2019-02-04 16:08   ` Winkler, Tomas
2019-01-31  6:59 ` [PATCH v10 20/40] drm/i915: Add HDCP2.2 support for HDMI connectors Ramalingam C
2019-02-04 16:04   ` Winkler, Tomas
2019-02-04 16:11     ` C, Ramalingam
2019-01-31  6:59 ` [PATCH v10 21/40] mei: bus: whitelist hdcp client Ramalingam C
2019-01-31  6:59 ` [PATCH v10 22/40] mei: bus: export to_mei_cl_device for mei client device drivers Ramalingam C
2019-01-31  6:59 ` [PATCH v10 23/40] misc/mei/hdcp: Client driver for HDCP application Ramalingam C
2019-02-05 12:33   ` Winkler, Tomas
2019-01-31  6:59 ` [PATCH v10 24/40] misc/mei/hdcp: Define ME FW interface for HDCP2.2 Ramalingam C
2019-02-04 16:07   ` Shankar, Uma
2019-02-05 13:01     ` Winkler, Tomas
2019-01-31  6:59 ` [PATCH v10 25/40] misc/mei/hdcp: Initiate Wired HDCP2.2 Tx Session Ramalingam C
2019-02-04 16:09   ` Shankar, Uma
2019-02-05 13:09     ` Winkler, Tomas
2019-02-05 14:13       ` C, Ramalingam [this message]
2019-02-06 10:27       ` Winkler, Tomas
2019-02-06 21:14         ` C, Ramalingam
2019-01-31  6:59 ` [PATCH v10 26/40] misc/mei/hdcp: Verify Receiver Cert and prepare km Ramalingam C
2019-02-04 16:10   ` Shankar, Uma
2019-02-06  8:28     ` Winkler, Tomas
2019-01-31  6:59 ` [PATCH v10 27/40] misc/mei/hdcp: Verify H_prime Ramalingam C
2019-02-04 16:11   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 28/40] misc/mei/hdcp: Store the HDCP Pairing info Ramalingam C
2019-02-04 16:13   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 29/40] misc/mei/hdcp: Initiate Locality check Ramalingam C
2019-02-04 16:16   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 30/40] misc/mei/hdcp: Verify L_prime Ramalingam C
2019-02-04 16:16   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 31/40] misc/mei/hdcp: Prepare Session Key Ramalingam C
2019-02-04 16:17   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 32/40] misc/mei/hdcp: Repeater topology verification and ack Ramalingam C
2019-02-04 16:17   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 33/40] misc/mei/hdcp: Verify M_prime Ramalingam C
2019-02-04 16:18   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 34/40] misc/mei/hdcp: Enabling the HDCP authentication Ramalingam C
2019-02-04 16:19   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 35/40] misc/mei/hdcp: Closing wired HDCP2.2 Tx Session Ramalingam C
2019-02-04 16:20   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 36/40] misc/mei/hdcp: Component framework for I915 Interface Ramalingam C
2019-01-31  8:23   ` Daniel Vetter
2019-02-04 16:27   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 37/40] drm/i915: Commit CP without modeset Ramalingam C
2019-01-31  8:32   ` Daniel Vetter
2019-02-04  8:39     ` C, Ramalingam
2019-01-31  6:59 ` [PATCH v10 38/40] drm/i915: Fix KBL HDCP2.2 encrypt status signalling Ramalingam C
2019-02-04 15:32   ` C, Ramalingam
2019-02-05  8:54     ` Daniel Vetter
2019-02-04 16:35   ` Shankar, Uma
2019-01-31  6:59 ` [PATCH v10 39/40] FOR_TEST: i915/Kconfig: Select mei_hdcp by I915 Ramalingam C
2019-01-31  6:59 ` [PATCH v10 40/40] FOR_TESTING_ONLY: debugfs: Excluding the LSPCon for HDCP1.4 Ramalingam C
2019-01-31  7:38 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Implement HDCP2.2 (rev13) Patchwork
2019-01-31  8:16 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-31 18:42 ` ✓ 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=c6a12119-3537-2d58-80b4-0f4b623a9ef9@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 \
    /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