From: Jani Nikula <jani.nikula@linux.intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915/hdcp: Add a debug statment at hdcp2 capability check
Date: Wed, 21 Jun 2023 10:28:25 +0300 [thread overview]
Message-ID: <87pm5pff52.fsf@intel.com> (raw)
In-Reply-To: <20230621014156.1994797-1-suraj.kandpal@intel.com>
On Wed, 21 Jun 2023, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> Add a debug statement at hdcp2 capability check which indicates if
> GSC CS is causing hdcp2 incapability
>
> --v2
> -correcting typo in commit header
Maybe fix the other typo as well? ;)
BR,
Jani.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_hdcp.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c b/drivers/gpu/drm/i915/display/intel_hdcp.c
> index 5ed450111f77..73fe84fc9bf5 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdcp.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
> @@ -177,8 +177,11 @@ bool intel_hdcp2_capable(struct intel_connector *connector)
> struct intel_gt *gt = i915->media_gt;
> struct intel_gsc_uc *gsc = gt ? >->uc.gsc : NULL;
>
> - if (!gsc || !intel_uc_fw_is_running(&gsc->fw))
> + if (!gsc || !intel_uc_fw_is_running(&gsc->fw)) {
> + drm_dbg_kms(&i915->drm,
> + "GSC components required for HDCP2.2 are not ready\n");
> return false;
> + }
> }
>
> /* MEI/GSC interface is solid depending on which is used */
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-06-21 7:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 1:35 [Intel-gfx] [PATCH] drm/i915/hdcp: Add a debug statment at hcdp2 capability check Suraj Kandpal
2023-06-21 1:41 ` [Intel-gfx] [PATCH v2] drm/i915/hdcp: Add a debug statment at hdcp2 " Suraj Kandpal
2023-06-21 7:28 ` Jani Nikula [this message]
2023-06-21 8:54 ` [Intel-gfx] [PATCH v3] drm/i915/hdcp: Add a debug statement " Suraj Kandpal
2023-06-22 13:53 ` Borah, Chaitanya Kumar
2023-06-22 14:00 ` Kandpal, Suraj
2023-06-22 14:11 ` Borah, Chaitanya Kumar
2023-06-21 5:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/hdcp: Add a debug statment at hcdp2 capability check (rev2) Patchwork
2023-06-21 17:05 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/hdcp: Add a debug statment at hcdp2 capability check (rev3) Patchwork
2023-06-22 10:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-22 19:36 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-06-23 5:34 ` Patchwork
2023-06-23 5:42 ` [Intel-gfx] ✓ Fi.CI.IGT: success " 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=87pm5pff52.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@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