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: Change log level for HDMI HDCP LIC check
Date: Thu, 28 Nov 2024 17:20:36 +0530 [thread overview]
Message-ID: <e5097d78-a55a-48e8-bf01-a1ec930f8caa@intel.com> (raw)
In-Reply-To: <20241128063427.1792509-1-suraj.kandpal@intel.com>
On 11/28/2024 12:04 PM, Suraj Kandpal wrote:
> We don't need to shout out loud if there is a Link Integrity
> Failure. This does not mean HDCP has failed, it is expected and
> taken into account in the HDCP Spec. The real failure happens when
> we are not able to reauthenticate and get HDCP running again for
> which we already have the right logging.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_hdmi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_hdmi.c b/drivers/gpu/drm/i915/display/intel_hdmi.c
> index 23c270a8c4aa..fa679b5d5510 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdmi.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdmi.c
> @@ -1607,7 +1607,7 @@ bool intel_hdmi_hdcp_check_link(struct intel_digital_port *dig_port,
> if (intel_hdmi_hdcp_check_link_once(dig_port, connector))
> return true;
>
> - drm_err(display->drm, "Link check failed\n");
> + drm_dbg_kms(display->drm, "Link check failed\n");
I agree, we do re-authentication after this so this is not an error at
this point.
We already have below debug message in case check_link() fails for
either hdmi/dp in intel_hdcp.c
drm_dbg_kms(display->drm,
"[CONNECTOR:%d:%s] HDCP link failed, retrying
authentication\n",
connector->base.base.id, connector->base.name);
Perhaps just dropping this message altogether will be better.
Regards,
Ankit
> return false;
> }
>
next prev parent reply other threads:[~2024-11-28 11:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 6:34 [PATCH] drm/i915/hdcp: Change log level for HDMI HDCP LIC check Suraj Kandpal
2024-11-28 6:40 ` ✓ CI.Patch_applied: success for " Patchwork
2024-11-28 6:40 ` ✓ CI.checkpatch: " Patchwork
2024-11-28 6:41 ` ✓ CI.KUnit: " Patchwork
2024-11-28 6:59 ` ✓ CI.Build: " Patchwork
2024-11-28 7:02 ` ✓ CI.Hooks: " Patchwork
2024-11-28 7:03 ` ✗ CI.checksparse: warning " Patchwork
2024-11-28 7:22 ` ✓ Xe.CI.BAT: success " Patchwork
2024-11-28 8:26 ` ✗ Xe.CI.Full: failure " Patchwork
2024-11-28 11:50 ` Nautiyal, Ankit K [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-29 9:05 [PATCH] " Suraj Kandpal
2024-11-29 12:43 ` kernel test robot
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=e5097d78-a55a-48e8-bf01-a1ec930f8caa@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