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: [PATCH v3 15/40] misc/mei/hdcp: Repeater topology verifcation and ack
Date: Wed, 16 May 2018 22:02:48 +0530 [thread overview]
Message-ID: <dbbe71d6-7d32-da3f-a34c-3c62dee40adb@intel.com> (raw)
In-Reply-To: <E7C9878FBA1C6D42A1CA3F62AEB6945F7F1EF854@BGSMSX104.gar.corp.intel.com>
On Wednesday 09 May 2018 04:34 PM, Shankar, Uma wrote:
>
>> -----Original Message-----
>> From: dri-devel [mailto:dri-devel-bounces@lists.freedesktop.org] On Behalf Of
>> Ramalingam C
>> Sent: Tuesday, April 3, 2018 7:27 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: [PATCH v3 15/40] misc/mei/hdcp: Repeater topology verifcation and ack
> Typo in verification.
>
>> Request ot ME to verify the downatream topology information received.
> "To" misspelled. Also typo in downstream.
ok. Will fix it.
>
>> ME FW will validate the Repeaters receiver id list and downstream topology.
>>
>> On Success ME FW will provide the Least Significant 128bits of VPrime, which
>> forms the repeater ack.
>>
>> v2:
>> Rebased.
>> v3:
>> cldev is passed as first parameter [Tomas]
>> Redundant comments and cast are removed [Tomas]
>>
>> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
>> ---
>> drivers/misc/mei/hdcp/mei_hdcp.c | 75
>> ++++++++++++++++++++++++++++++++++++++++
>> include/linux/mei_hdcp.h | 15 ++++++++
>> 2 files changed, 90 insertions(+)
>>
>> diff --git a/drivers/misc/mei/hdcp/mei_hdcp.c
>> b/drivers/misc/mei/hdcp/mei_hdcp.c
>> index abfcc57863b8..64fcecfa5b10 100644
>> --- a/drivers/misc/mei/hdcp/mei_hdcp.c
>> +++ b/drivers/misc/mei/hdcp/mei_hdcp.c
>> @@ -478,6 +478,81 @@ int mei_get_session_key(struct mei_cl_device *cldev,
>> struct mei_hdcp_data *data, } EXPORT_SYMBOL(mei_get_session_key);
>>
>> +/**
>> + * mei_repeater_check_flow_prepare_ack:
>> + * Function to validate the Downstream topology and prepare rep_ack.
>> + *
>> + * @cldev : Pointer for mei client device
>> + * @data : Intel HW specific Data
>> + * @rep_topology : Pointer for Receiver Id List to be validated.
>> + * @rep_send_ack : Pointer for repeater ack
>> + *
>> + * Returns 0 on Success, <0 on Failure
>> + */
>> +
>> +int
>> +mei_repeater_check_flow_prepare_ack(struct mei_cl_device *cldev,
>> + struct mei_hdcp_data *data,
>> + struct hdcp2_rep_send_receiverid_list
>> + *rep_topology,
>> + struct hdcp2_rep_send_ack *rep_send_ack) {
>> + struct wired_cmd_verify_repeater_in verify_repeater_in = { { 0 } };
>> + struct wired_cmd_verify_repeater_out verify_repeater_out = { { 0 } };
>> + struct device *dev;
>> + ssize_t byte;
>> +
>> + if (!rep_topology || !rep_send_ack || !data)
>> + return -EINVAL;
>> +
>> + dev = &cldev->dev;
>> +
>> + verify_repeater_in.header.api_version = HDCP_API_VERSION;
>> + verify_repeater_in.header.command_id = WIRED_VERIFY_REPEATER;
>> + verify_repeater_in.header.status = ME_HDCP_STATUS_SUCCESS;
>> + verify_repeater_in.header.buffer_len =
>> +
>> WIRED_CMD_BUF_LEN_VERIFY_REPEATER_IN;
>> +
>> + verify_repeater_in.port.integrated_port_type = data->port_type;
>> + verify_repeater_in.port.physical_port = data->port;
>> +
>> + memcpy(verify_repeater_in.rx_info, rep_topology->rx_info,
>> + HDCP_2_2_RXINFO_LEN);
>> + memcpy(verify_repeater_in.seq_num_v, rep_topology->seq_num_v,
>> + HDCP_2_2_SEQ_NUM_LEN);
>> + memcpy(verify_repeater_in.v_prime, rep_topology->v_prime,
>> + HDCP_2_2_LPRIME_HALF_LEN);
>> + memcpy(verify_repeater_in.receiver_ids, rep_topology->receiver_ids,
>> + HDCP_2_2_RECEIVER_IDS_MAX_LEN);
> Check for validity of rep_topology->... pointers.
>
>> +
>> + byte = mei_cldev_send(cldev, (u8 *)&verify_repeater_in,
>> + sizeof(verify_repeater_in));
>> + if (byte < 0) {
>> + dev_dbg(dev, "mei_cldev_send failed. %d\n", (int)byte);
>> + return byte;
>> + }
>> +
>> + byte = mei_cldev_recv(cldev, (u8 *)&verify_repeater_out,
>> + sizeof(verify_repeater_out));
>> + if (byte < 0) {
>> + dev_dbg(dev, "mei_cldev_recv failed. %d\n", (int)byte);
>> + return byte;
>> + }
>> +
>> + if (verify_repeater_out.header.status != ME_HDCP_STATUS_SUCCESS) {
>> + dev_dbg(dev, "ME cmd 0x%08X failed. status: 0x%X\n",
>> + WIRED_VERIFY_REPEATER,
>> + verify_repeater_out.header.status);
>> + return -1;
>> + }
>> +
>> + memcpy(rep_send_ack->v, verify_repeater_out.v,
> Same as above.
>
>> + HDCP_2_2_LPRIME_HALF_LEN);
>> + rep_send_ack->msg_id = HDCP_2_2_REP_SEND_ACK;
> Leave a blank line here.
Ok.
--Ram
>
>> + return 0;
>> +}
>> +EXPORT_SYMBOL(mei_repeater_check_flow_prepare_ack);
>> +
>> void mei_cldev_state_notify_clients(struct mei_cl_device *cldev, bool enabled) {
>> if (enabled)
>> diff --git a/include/linux/mei_hdcp.h b/include/linux/mei_hdcp.h index
>> 534170d746af..46e2dc295d03 100644
>> --- a/include/linux/mei_hdcp.h
>> +++ b/include/linux/mei_hdcp.h
>> @@ -128,6 +128,12 @@ int mei_verify_lprime(struct mei_cl_device *cldev,
>> struct mei_hdcp_data *data,
>> struct hdcp2_lc_send_lprime *rx_lprime); int
>> mei_get_session_key(struct mei_cl_device *cldev, struct mei_hdcp_data *data,
>> struct hdcp2_ske_send_eks *ske_data);
>> +int
>> +mei_repeater_check_flow_prepare_ack(struct mei_cl_device *cldev,
>> + struct mei_hdcp_data *data,
>> + struct hdcp2_rep_send_receiverid_list
>> + *rep_topology,
>> + struct hdcp2_rep_send_ack *rep_send_ack);
>> #else
>> static int mei_cldev_register_notify(struct notifier_block *nb) { @@ -186,5
>> +192,14 @@ int mei_get_session_key(struct mei_cl_device *cldev, struct
>> mei_hdcp_data *data, {
>> return -ENODEV;
>> }
>> +static inline int
>> +mei_repeater_check_flow_prepare_ack(struct mei_cl_device *cldev,
>> + struct mei_hdcp_data *data,
>> + struct hdcp2_rep_send_receiverid_list
>> + *rep_topology,
>> + struct hdcp2_rep_send_ack *rep_send_ack) {
>> + return -ENODEV;
>> +}
>> #endif /* defined (CONFIG_INTEL_MEI_HDCP) */ #endif /* defined
>> (_LINUX_MEI_HDCP_H) */
>> --
>> 2.7.4
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
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-16 16:32 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 [this message]
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 ` [Intel-gfx] " Ramalingam C
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=dbbe71d6-7d32-da3f-a34c-3c62dee40adb@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).