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 3/4] drm/i915: debugfs info print "HDCP shim isn't available"
Date: Fri, 7 Feb 2020 19:43:37 +0530 [thread overview]
Message-ID: <20200207141337.GE11460@intel.com> (raw)
In-Reply-To: <20200128135425.14596-4-anshuman.gupta@intel.com>
On 2020-01-28 at 19:24:24 +0530, Anshuman Gupta wrote:
> If HDCP shim is not initialized, i915_display_info
> connector info returns EINVAL without providing any debug
> information. Adding a print for that will be useful for debugging.
>
> CC: Ramalingam C <ramalingam.c@intel.com>
> Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index 0ac98e39eb75..6d913a71cbdb 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -2405,7 +2405,8 @@ static void intel_dp_info(struct seq_file *m,
> if (intel_connector->hdcp.shim) {
> seq_puts(m, "\tHDCP version: ");
> intel_hdcp_info(m, intel_connector);
> - }
> + } else if (!intel_dp_is_edp(intel_dp))
> + seq_puts(m, "\tHDCP shim isn't available\n");
I would prefer "HDCP shim is not initialized" for this purpose.
But when this can happen on DP/HDCP connector? Either has_hdcp is false
or when port is >= E. Those info might help better for debugging.
Infact as we discussed in other patch, we need to check whether we need\
port limitation for <gen12.
-Ram
> }
>
> static void intel_dp_mst_info(struct seq_file *m,
> @@ -2432,6 +2433,8 @@ static void intel_hdmi_info(struct seq_file *m,
> if (intel_connector->hdcp.shim) {
> seq_puts(m, "\tHDCP version: ");
> intel_hdcp_info(m, intel_connector);
> + } else {
> + seq_puts(m, "\tHDCP shim isn't available\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-07 14:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 13:54 [Intel-gfx] [PATCH 0/4] HDCP Misc series Anshuman Gupta
2020-01-28 13:54 ` [Intel-gfx] [PATCH 1/4] drm/i915/hdcp: Update CP as per the kernel internal state Anshuman Gupta
2020-01-28 14:19 ` Jani Nikula
2020-01-28 15:44 ` Anshuman Gupta
2020-01-28 16:15 ` Anshuman Gupta
2020-02-05 5:07 ` Anshuman Gupta
2020-03-03 14:36 ` Maarten Lankhorst
2020-03-03 16:35 ` Anshuman Gupta
2020-03-04 8:43 ` Maarten Lankhorst
2020-03-05 5:56 ` Anshuman Gupta
2020-01-28 13:54 ` [Intel-gfx] [PATCH 2/4] drm/i915: HDCP support on above PORT_E Anshuman Gupta
2020-01-28 14:20 ` Jani Nikula
2020-01-28 14:21 ` Jani Nikula
2020-01-29 13:26 ` [Intel-gfx] [PATCH v2 " Anshuman Gupta
2020-02-07 14:03 ` Ramalingam C
2020-01-28 13:54 ` [Intel-gfx] [PATCH 3/4] drm/i915: debugfs info print "HDCP shim isn't available" Anshuman Gupta
2020-02-07 14:13 ` Ramalingam C [this message]
2020-01-28 13:54 ` [Intel-gfx] [PATCH 4/4] drm/i915: Add HDCP2.2 capable debug print Anshuman Gupta
2020-01-28 14:23 ` Jani Nikula
2020-02-07 14:16 ` Ramalingam C
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=20200207141337.GE11460@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