From: Ramalingam C <ramalingam.c@intel.com>
To: Anshuman Gupta <anshuman.gupta@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 1/1] drm/i915/hdcp: Mandate zero seq_num_V at first RecvId msg
Date: Thu, 13 Feb 2020 13:53:29 +0530 [thread overview]
Message-ID: <20200213082329.GA13448@intel.com> (raw)
In-Reply-To: <20200212084143.13852-2-anshuman.gupta@intel.com>
On 2020-02-12 at 14:11:43 +0530, Anshuman Gupta wrote:
> HDCP Repeater initializes seq_num_V to 0 at the beginning of
> hdcp Session i.e. after AKE_init received, refer
> HDCP 2.2 Spec HDMI PAGE 19, DP PAGE 20.
>
> HDCP 2.2 Comp specs 1B-06 test verifies that whether DUT
> considers failure of authentication if the repeater provides a
> non-zero value in seq_num_V in the first,
> RepeaterAuth_Send_ReceiverID_List message.
>
> Make sure that HDCP repeater initializes seq_num_V to zero at
> beginning of session i.e. after AKE_Init, fail the Auth if
> there is non zero seq_num_V.
>
> v2:
> - Used existing hdcp2_encrypted flag instead of
> declaring new flag. [Ram]
>
> Cc: Ramalingam C <ramalingam.c@intel.com>
> Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_hdcp.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c b/drivers/gpu/drm/i915/display/intel_hdcp.c
> index 30e0a3aa9d57..75f60ca282fc 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdcp.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
> @@ -1462,6 +1462,12 @@ int hdcp2_authenticate_repeater_topology(struct intel_connector *connector)
> seq_num_v =
> drm_hdcp_be24_to_cpu((const u8 *)msgs.recvid_list.seq_num_v);
>
> + if (!hdcp->hdcp2_encrypted && seq_num_v) {
> + drm_dbg_kms(&dev_priv->drm,
> + "Non zero Seq_num_v at first RecvId_List msg\n");
> + return -EINVAL;
> + }
> +
As we dont have retry for topology authentication alone and it always
start with AKE_Init, we can rely on hdcp2_encrypted status for first
RepeaterAuth_Send_ReceiverID_List detection.
LGTM.
Reviewed-by: Ramalingam C <ramalingam.c@intel.com>
> if (seq_num_v < hdcp->seq_num_v) {
> /* Roll over of the seq_num_v from repeater. Reauthenticate. */
> DRM_DEBUG_KMS("Seq_num_v roll over.\n");
> --
> 2.24.0
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-02-13 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 8:41 [Intel-gfx] [PATCH v2 0/1] HDCP 2.2 Comp fixes Anshuman Gupta
2020-02-12 8:41 ` [Intel-gfx] [PATCH v2 1/1] drm/i915/hdcp: Mandate zero seq_num_V at first RecvId msg Anshuman Gupta
2020-02-13 8:23 ` Ramalingam C [this message]
2020-02-12 13:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success for HDCP 2.2 Comp fixes Patchwork
2020-02-14 7:09 ` [Intel-gfx] ✓ 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=20200213082329.GA13448@intel.com \
--to=ramalingam.c@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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