From: Ramalingam C <ramalingam.c@intel.com>
To: "Shankar, Uma" <uma.shankar@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"seanpaul@chromium.org" <seanpaul@chromium.org>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
"Winkler, Tomas" <tomas.winkler@intel.com>,
"Usyskin, Alexander" <alexander.usyskin@intel.com>
Cc: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH v3 22/40] drm/i915: Wrappers for mei HDCP2.2 services
Date: Thu, 17 May 2018 16:10:54 +0530 [thread overview]
Message-ID: <3ef5e24f-eabb-3b08-3fc0-86131169ee4b@intel.com> (raw)
In-Reply-To: <E7C9878FBA1C6D42A1CA3F62AEB6945F7F1EFB4D@BGSMSX104.gar.corp.intel.com>
On Wednesday 09 May 2018 08:40 PM, Shankar, Uma wrote:
>
>> -----Original Message-----
>> From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf Of
>> Ramalingam C
>> Sent: Tuesday, April 3, 2018 7:28 PM
>> To: intel-gfx@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
>> seanpaul@chromium.org; daniel@ffwll.ch; chris@chris-wilson.co.uk;
>> jani.nikula@linux.intel.com; Winkler, Tomas <tomas.winkler@intel.com>;
>> Usyskin, Alexander <alexander.usyskin@intel.com>
>> Cc: Vivi, Rodrigo <rodrigo.vivi@intel.com>
>> Subject: [Intel-gfx] [PATCH v3 22/40] drm/i915: Wrappers for mei HDCP2.2
>> services
>>
>> Adds the wrapper for all mei hdcp2.2 service functions.
>>
>> v2:
>> Rebased.
>> v3:
>> cldev is moved from mei_hdcp_data to hdcp.
>>
>> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
>> ---
>> drivers/gpu/drm/i915/intel_hdcp.c | 194
>> ++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 194 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_hdcp.c
>> b/drivers/gpu/drm/i915/intel_hdcp.c
>> index 1cca4f349064..b4d56b21cf9b 100644
>> --- a/drivers/gpu/drm/i915/intel_hdcp.c
>> +++ b/drivers/gpu/drm/i915/intel_hdcp.c
>> @@ -10,10 +10,13 @@
>> #include <drm/drm_hdcp.h>
>> #include <linux/i2c.h>
>> #include <linux/random.h>
>> +#include <linux/mei_hdcp.h>
>>
>> #include "intel_drv.h"
>> #include "i915_reg.h"
>>
>> +#define GET_MEI_DDI_INDEX(port) (((port) == PORT_A) ? DDI_A : \
>> + (enum hdcp_physical_port) (port))
>> #define KEY_LOAD_TRIES 5
>>
>> static int intel_hdcp_poll_ksv_fifo(struct intel_digital_port *intel_dig_port, @@ -
>> 817,3 +820,194 @@ int intel_hdcp_check_link(struct intel_connector
>> *connector)
>> mutex_unlock(&hdcp->hdcp_mutex);
>> return ret;
>> }
>> +
>> +static int
>> +hdcp2_prepare_ake_init(struct intel_hdcp *hdcp, struct hdcp2_ake_init
>> +*ake_data) {
>> + struct mei_hdcp_data *data = &hdcp->mei_data;
>> + struct intel_connector *connector = container_of(hdcp,
>> + struct intel_connector,
>> + hdcp);
>> +
>> + if (!hdcp->cldev)
>> + return -EINVAL;
>> +
>> + if (data->port == INVALID_PORT && connector->encoder)
>> + data->port = GET_MEI_DDI_INDEX(connector->encoder->port);
> I believe caller should provide valid port and this should fail if port received is invalid instead of
> retrieving it here.
Agreed. But at the initialization of mei_hdcp_data, if the encoder is
not initialized, data->port will be uninitialized (invalid).
So in that case at the start of the hdcp authentication we initialize
the port. May be I am bit paranoid here!
But on all other wrappers port needs to be valid.
--Ram
>> +
>> + /* Clear ME FW instance for the port, just incase */
>> + mei_close_hdcp_session(hdcp->cldev, data);
>> +
>> + return mei_initiate_hdcp2_session(hdcp->cldev, data, ake_data); }
>> +
>> +static int hdcp2_close_mei_session(struct intel_hdcp *hdcp) {
>> + struct mei_hdcp_data *data = &hdcp->mei_data;
>> +
>> + if (!hdcp->cldev || data->port == INVALID_PORT)
> This is what I was saying for above.
>
>> + return -EINVAL;
>> +
>> + return mei_close_hdcp_session(hdcp->cldev, data); }
>> +
>> +static int
>> +hdcp2_verify_rx_cert_prepare_km(struct intel_hdcp *hdcp,
>> + struct hdcp2_ake_send_cert *rx_cert,
>> + bool *paired,
>> + struct hdcp2_ake_no_stored_km *ek_pub_km,
>> + size_t *msg_sz)
>> +{
>> + struct mei_hdcp_data *data = &hdcp->mei_data;
>> + int ret;
>> +
>> + if (!hdcp->cldev)
>> + return -EINVAL;
>> +
>> + ret = mei_verify_receiver_cert_prepare_km(hdcp->cldev, data, rx_cert,
>> + paired, ek_pub_km, msg_sz);
>> + if (ret < 0)
>> + mei_close_hdcp_session(hdcp->cldev, data);
>> +
>> + return ret;
>> +}
>> +
>> +static int hdcp2_verify_hprime(struct intel_hdcp *hdcp,
>> + struct hdcp2_ake_send_hprime *rx_hprime) {
>> + struct mei_hdcp_data *data = &hdcp->mei_data;
>> + int ret;
>> +
>> + if (!hdcp->cldev)
>> + return -EINVAL;
>> +
>> + ret = mei_verify_hprime(hdcp->cldev, data, rx_hprime);
>> + if (ret < 0)
>> + mei_close_hdcp_session(hdcp->cldev, data);
>> +
>> + return ret;
>> +}
>> +
>> +static int
>> +hdcp2_store_paring_info(struct intel_hdcp *hdcp,
>> + struct hdcp2_ake_send_pairing_info *pairing_info) {
>> + struct mei_hdcp_data *data = &hdcp->mei_data;
>> + int ret;
>> +
>> + if (!hdcp->cldev)
>> + return -EINVAL;
>> +
>> + ret = mei_store_pairing_info(hdcp->cldev, data, pairing_info);
>> + if (ret < 0)
>> + mei_close_hdcp_session(hdcp->cldev, data);
>> +
>> + return ret;
>> +}
>> +
>> +static int
>> +hdcp2_prepare_lc_init(struct intel_hdcp *hdcp, struct hdcp2_lc_init
>> +*lc_init) {
>> + struct mei_hdcp_data *data = &hdcp->mei_data;
>> + int ret;
>> +
>> + if (!hdcp->cldev)
>> + return -EINVAL;
>> +
>> + ret = mei_initiate_locality_check(hdcp->cldev, data, lc_init);
>> + if (ret < 0)
>> + mei_close_hdcp_session(hdcp->cldev, data);
>> +
>> + return ret;
>> +}
>> +
>> +static int
>> +hdcp2_verify_lprime(struct intel_hdcp *hdcp,
>> + struct hdcp2_lc_send_lprime *rx_lprime) {
>> + struct mei_hdcp_data *data = &hdcp->mei_data;
>> + int ret;
>> +
>> + if (!hdcp->cldev)
>> + return -EINVAL;
>> +
>> + ret = mei_verify_lprime(hdcp->cldev, data, rx_lprime);
>> + if (ret < 0)
>> + mei_close_hdcp_session(hdcp->cldev, data);
>> +
>> + return ret;
>> +}
>> +
>> +static int hdcp2_prepare_skey(struct intel_hdcp *hdcp,
>> + struct hdcp2_ske_send_eks *ske_data) {
>> + struct mei_hdcp_data *data = &hdcp->mei_data;
>> + int ret;
>> +
>> + if (!hdcp->cldev)
>> + return -EINVAL;
>> +
>> + ret = mei_get_session_key(hdcp->cldev, data, ske_data);
>> + if (ret < 0)
>> + mei_close_hdcp_session(hdcp->cldev, data);
>> +
>> + return ret;
>> +}
>> +
>> +static int
>> +hdcp2_verify_rep_topology_prepare_ack(
>> + struct intel_hdcp *hdcp,
>> + struct hdcp2_rep_send_receiverid_list *rep_topology,
>> + struct hdcp2_rep_send_ack *rep_send_ack) {
>> + struct mei_hdcp_data *data = &hdcp->mei_data;
>> + int ret;
>> +
>> + if (!hdcp->cldev)
>> + return -EINVAL;
>> +
>> + ret = mei_repeater_check_flow_prepare_ack(hdcp->cldev, data,
>> + rep_topology, rep_send_ack);
>> + if (ret < 0)
>> + mei_close_hdcp_session(hdcp->cldev, data);
>> +
>> + return ret;
>> +}
>> +
>> +static int
>> +hdcp2_verify_mprime(struct intel_hdcp *hdcp,
>> + struct hdcp2_rep_stream_ready *stream_ready) {
>> + struct mei_hdcp_data *data = &hdcp->mei_data;
>> + int ret;
>> +
>> + if (!hdcp->cldev)
>> + return -EINVAL;
>> +
>> + ret = mei_verify_mprime(hdcp->cldev, data, stream_ready);
>> + if (ret < 0)
>> + mei_close_hdcp_session(hdcp->cldev, data);
>> +
>> + return ret;
>> +}
>> +
>> +
>> +static int hdcp2_authenticate_port(struct intel_hdcp *hdcp) {
>> + struct mei_hdcp_data *data = &hdcp->mei_data;
>> + int ret;
>> +
>> + if (!hdcp->cldev)
>> + return -EINVAL;
>> +
>> + ret = mei_enable_hdcp_authentication(hdcp->cldev, data);
>> + if (ret < 0)
>> + mei_close_hdcp_session(hdcp->cldev, data);
>> +
>> + return ret;
>> +}
>> +
>> +static inline int hdcp2_deauthenticate_port(struct intel_hdcp *hdcp) {
>> + return hdcp2_close_mei_session(hdcp);
>> +}
>> --
>> 2.7.4
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-17 10:40 UTC|newest]
Thread overview: 129+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 13:57 [PATCH v3 00/40] drm/i915: Implement HDCP2.2 Ramalingam C
2018-04-03 13:57 ` [PATCH v3 01/40] drm: hdcp2.2 authentication msg definitions Ramalingam C
2018-05-09 10:01 ` Shankar, Uma
2018-05-14 15:23 ` [Intel-gfx] " Ramalingam C
2018-04-03 13:57 ` [PATCH v3 02/40] drm: HDMI and DP specific HDCP2.2 defines Ramalingam C
2018-05-09 10:06 ` Shankar, Uma
2018-05-14 16:01 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 03/40] mei: bus: whitelist hdcp client Ramalingam C
2018-04-03 13:57 ` [PATCH v3 04/40] misc/mei/hdcp: Client driver for HDCP application Ramalingam C
2018-05-09 10:07 ` Shankar, Uma
2018-04-03 13:57 ` [PATCH v3 05/40] misc/mei/hdcp: Notifier chain for mei cldev state change Ramalingam C
2018-04-03 15:30 ` Daniel Vetter
2018-05-16 14:54 ` Ramalingam C
2018-04-03 20:53 ` kbuild test robot
2018-04-03 23:58 ` [RFC PATCH] misc/mei/hdcp: mei_cldev_state_notify_clients() can be static kbuild test robot
2018-04-04 6:12 ` [PATCH v3 05/40] misc/mei/hdcp: Notifier chain for mei cldev state change Usyskin, Alexander
2018-05-16 13:04 ` Ramalingam C
2018-05-17 5:52 ` Usyskin, Alexander
2018-05-17 6:15 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 06/40] misc/mei/hdcp: Define ME FW interface for HDCP2.2 Ramalingam C
2018-04-03 13:57 ` [PATCH v3 07/40] linux/mei: Header for mei_hdcp driver interface Ramalingam C
2018-05-09 10:08 ` Shankar, Uma
2018-05-16 15:05 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 08/40] misc/mei/hdcp: Initiate Wired HDCP2.2 Tx Session Ramalingam C
2018-04-03 21:20 ` [Intel-gfx] " kbuild test robot
2018-04-04 6:45 ` Usyskin, Alexander
2018-05-16 15:19 ` Ramalingam C
2018-05-17 5:56 ` Usyskin, Alexander
2018-05-17 6:08 ` Ramalingam C
2018-05-09 10:13 ` Shankar, Uma
2018-05-16 15:26 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 09/40] misc/mei/hdcp: Verify Receiver Cert and prepare km Ramalingam C
2018-04-03 21:44 ` kbuild test robot
2018-04-03 13:57 ` [PATCH v3 10/40] misc/mei/hdcp: Verify H_prime Ramalingam C
2018-04-03 22:12 ` kbuild test robot
2018-05-09 10:16 ` [Intel-gfx] " Shankar, Uma
2018-05-16 15:43 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 11/40] misc/mei/hdcp: Store the HDCP Pairing info Ramalingam C
2018-04-03 22:34 ` kbuild test robot
2018-05-09 10:28 ` Shankar, Uma
2018-05-16 15:53 ` Ramalingam C
2018-05-17 5:59 ` Usyskin, Alexander
2018-05-17 6:03 ` C, Ramalingam
2018-05-17 8:17 ` Jani Nikula
2018-05-21 12:19 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 12/40] misc/mei/hdcp: Initiate Locality check Ramalingam C
2018-04-03 23:02 ` kbuild test robot
2018-05-09 10:31 ` Shankar, Uma
2018-05-16 16:02 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 13/40] misc/mei/hdcp: Verify L_prime Ramalingam C
2018-05-09 10:36 ` Shankar, Uma
2018-05-16 16:05 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 14/40] misc/mei/hdcp: Prepare Session Key Ramalingam C
2018-05-09 10:59 ` Shankar, Uma
2018-05-16 16:10 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 15/40] misc/mei/hdcp: Repeater topology verifcation and ack Ramalingam C
2018-05-09 11:04 ` Shankar, Uma
2018-05-16 16:32 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 16/40] misc/mei/hdcp: Verify M_prime Ramalingam C
2018-05-09 13:50 ` Shankar, Uma
2018-05-16 16:32 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 17/40] misc/mei/hdcp: Enabling the HDCP authentication Ramalingam C
2018-05-09 13:55 ` Shankar, Uma
2018-05-16 16:40 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 18/40] misc/mei/hdcp: Closing wired HDCP2.2 Tx Session Ramalingam C
2018-05-09 14:02 ` [Intel-gfx] " Shankar, Uma
2018-05-16 16:41 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 19/40] drm/i915: wrapping all hdcp var into intel_hdcp Ramalingam C
2018-05-09 14:11 ` Shankar, Uma
2018-04-03 13:57 ` [PATCH v3 20/40] drm/i915: Define HDCP2.2 related variables Ramalingam C
2018-04-03 20:27 ` kbuild test robot
2018-05-09 14:23 ` Shankar, Uma
2018-04-03 13:57 ` [PATCH v3 21/40] drm/i915: Define Intel HDCP2.2 registers Ramalingam C
2018-05-09 14:59 ` Shankar, Uma
2018-05-17 10:24 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 22/40] drm/i915: Wrappers for mei HDCP2.2 services Ramalingam C
2018-05-09 15:10 ` Shankar, Uma
2018-05-17 10:40 ` Ramalingam C [this message]
2018-04-03 13:57 ` [PATCH v3 23/40] drm/i915: Implement HDCP2.2 receiver authentication Ramalingam C
2018-05-09 15:20 ` Shankar, Uma
2018-04-03 13:57 ` [PATCH v3 24/40] drm/i915: Implement HDCP2.2 repeater authentication Ramalingam C
2018-04-04 1:11 ` kbuild test robot
2018-05-14 9:08 ` Shankar, Uma
2018-05-17 12:38 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 25/40] drm/i915: Enable and Disable HDCP2.2 port encryption Ramalingam C
2018-05-14 9:23 ` Shankar, Uma
2018-05-17 13:01 ` Ramalingam C
2018-05-17 13:14 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 26/40] drm/i915: Implement HDCP2.2 En/Dis-able Ramalingam C
2018-05-14 9:30 ` Shankar, Uma
2018-05-17 13:16 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 27/40] drm/i915: Implement HDCP2.2 link integrity check Ramalingam C
2018-05-14 9:45 ` Shankar, Uma
2018-05-17 13:31 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 28/40] drm/i915: Handle HDCP2.2 downstream topology change Ramalingam C
2018-05-18 12:09 ` Shankar, Uma
2018-04-03 13:57 ` [PATCH v3 29/40] drm/i915: Pullout the bksv read and validation Ramalingam C
2018-04-03 13:57 ` [PATCH v3 30/40] drm/i915: Initialize HDCP2.2 and its MEI interface Ramalingam C
2018-05-18 12:33 ` [Intel-gfx] " Shankar, Uma
2018-05-18 16:29 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 31/40] drm/i915: Schedule hdcp_check_link in _intel_hdcp_enable Ramalingam C
2018-05-18 12:37 ` [Intel-gfx] " Shankar, Uma
2018-04-03 13:57 ` [PATCH v3 32/40] drm/i915: Enable superior HDCP ver that is capable Ramalingam C
2018-05-18 12:49 ` [Intel-gfx] " Shankar, Uma
2018-05-21 8:29 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 33/40] drm/i915: Enable HDCP1.4 incase of HDCP2.2 failure Ramalingam C
2018-05-18 12:52 ` Shankar, Uma
2018-04-03 13:57 ` [PATCH v3 34/40] drm/i915: hdcp_check_link only on CP_IRQ Ramalingam C
2018-05-18 12:55 ` Shankar, Uma
2018-04-03 13:57 ` [PATCH v3 35/40] drm/i915: Check HDCP 1.4 and 2.2 link " Ramalingam C
2018-05-18 15:59 ` Shankar, Uma
2018-05-21 8:37 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 36/40] drm/i915: Implement gmbus burst read Ramalingam C
2018-04-03 16:40 ` Daniel Vetter
2018-04-05 9:12 ` Jani Nikula
2018-04-05 13:44 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 37/40] drm/i915: Implement the HDCP2.2 support for DP Ramalingam C
2018-04-03 19:57 ` kbuild test robot
2018-04-03 21:16 ` kbuild test robot
2018-05-18 16:15 ` Shankar, Uma
2018-05-21 8:49 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 38/40] drm/i915: Implement the HDCP2.2 support for HDMI Ramalingam C
2018-05-18 16:29 ` Shankar, Uma
2018-05-21 9:08 ` [Intel-gfx] " Ramalingam C
2018-04-03 13:57 ` [PATCH v3 39/40] drm/i915: Add HDCP2.2 support for DP connectors Ramalingam C
2018-05-18 16:37 ` [Intel-gfx] " Shankar, Uma
2018-05-21 9:14 ` Ramalingam C
2018-04-03 13:57 ` [PATCH v3 40/40] drm/i915: Add HDCP2.2 support for HDMI connectors Ramalingam C
2018-05-18 16:38 ` [Intel-gfx] " 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=3ef5e24f-eabb-3b08-3fc0-86131169ee4b@intel.com \
--to=ramalingam.c@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).