From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
<intel-xe@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/hdcp: Fix Repeater authentication during topology change
Date: Fri, 17 Jan 2025 09:40:45 +0530 [thread overview]
Message-ID: <969c38ce-3dcd-430d-a8f2-85b73540ce6f@intel.com> (raw)
In-Reply-To: <20241217083723.2883317-1-suraj.kandpal@intel.com>
On 12/17/2024 2:07 PM, Suraj Kandpal wrote:
> When topology changes before beginning a new HDCP authentication by
> sending AKE_init message we need to first authenticate only the
> repeater if that fails only then makes sense to enable a new HDCP
> authentication. Even though it made sense to not enable HDCP directly
> from check_link and schedule it repeater authentication needs to be
> done immidieatly
typo: immediately
The first line seems to be overly long.
>
> Fixes: 47ef55a8b784 ("drm/i915/hdcp: Don't enable HDCP2.2 directly from check_link")
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Apart from the nitpicks, patch looks good to me.
Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_hdcp.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c b/drivers/gpu/drm/i915/display/intel_hdcp.c
> index f6e68a0e3b6d..9ff2274ed7e7 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdcp.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
> @@ -2182,6 +2182,19 @@ static int intel_hdcp2_check_link(struct intel_connector *connector)
>
> drm_dbg_kms(display->drm,
> "HDCP2.2 Downstream topology change\n");
> +
> + ret = hdcp2_authenticate_repeater_topology(connector);
> + if (!ret) {
> + intel_hdcp_update_value(connector,
> + DRM_MODE_CONTENT_PROTECTION_ENABLED,
> + true);
> + goto out;
> + }
> +
> + drm_dbg_kms(display->drm,
> + "[CONNECTOR:%d:%s] Repeater topology auth failed.(%d)\n",
> + connector->base.base.id, connector->base.name,
> + ret);
> } else {
> drm_dbg_kms(display->drm,
> "[CONNECTOR:%d:%s] HDCP2.2 link failed, retrying auth\n",
prev parent reply other threads:[~2025-01-17 4:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 8:37 [PATCH] drm/i915/hdcp: Fix Repeater authentication during topology change Suraj Kandpal
2024-12-17 8:55 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-17 8:55 ` ✓ CI.checkpatch: " Patchwork
2024-12-17 8:56 ` ✓ CI.KUnit: " Patchwork
2024-12-17 9:14 ` ✓ CI.Build: " Patchwork
2024-12-17 9:16 ` ✓ CI.Hooks: " Patchwork
2024-12-17 9:18 ` ✓ CI.checksparse: " Patchwork
2024-12-17 10:06 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-17 16:56 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-17 4:17 ` Kandpal, Suraj
2025-01-17 4:17 ` Kandpal, Suraj
2025-01-17 4:10 ` Nautiyal, Ankit K [this message]
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=969c38ce-3dcd-430d-a8f2-85b73540ce6f@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=suraj.kandpal@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