From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: <uma.shankar@intel.com>
Subject: Re: [PATCH 06/11] drm/i915/hdcp: HDCP Capability for the downstream device
Date: Fri, 2 Feb 2024 15:26:08 +0530 [thread overview]
Message-ID: <6fc619ad-96dd-4c45-8728-73f726fa555c@intel.com> (raw)
In-Reply-To: <20240202063852.1076862-7-suraj.kandpal@intel.com>
On 2/2/2024 12:08 PM, Suraj Kandpal wrote:
> Currently we are only checking capability of remote device and not
> immediate downstream device but during capability check we need are
> concerned with only the HDCP capability of downstream device.
> During i915_display_info reporting we need HDCP Capability for both
> the monitors and downstream branch device if any this patch adds that.
>
> --v2
> -Use MST Hub HDCP version [Ankit]
>
> --v3
> -Redefined how we seprate remote and direct read to make sure HDMI
> shim functions are not touched [Ankit]
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> .../drm/i915/display/intel_display_debugfs.c | 26 +++++++++++++++----
> 1 file changed, 21 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> index 6f2d13c8ccf7..41458f1cae38 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> @@ -188,7 +188,8 @@ static void intel_panel_info(struct seq_file *m,
> }
>
> static void intel_hdcp_info(struct seq_file *m,
> - struct intel_connector *intel_connector)
> + struct intel_connector *intel_connector,
> + bool remote_req)
> {
> bool hdcp_cap, hdcp2_cap;
>
> @@ -197,8 +198,13 @@ static void intel_hdcp_info(struct seq_file *m,
> goto out;
> }
>
> - hdcp_cap = intel_hdcp_capable(intel_connector);
> - hdcp2_cap = intel_hdcp2_capable(intel_connector);
> + if (remote_req) {
> + intel_hdcp_remote_cap(intel_connector, &hdcp_cap,
> + &hdcp2_cap);
> + } else {
> + hdcp_cap = intel_hdcp_capable(intel_connector);
> + hdcp2_cap = intel_hdcp2_capable(intel_connector);
> + }
>
> if (hdcp_cap)
> seq_puts(m, "HDCP1.4 ");
> @@ -285,7 +291,12 @@ static void intel_connector_info(struct seq_file *m,
> }
>
> seq_puts(m, "\tHDCP version: ");
> - intel_hdcp_info(m, intel_connector);
> + intel_hdcp_info(m, intel_connector, true);
This seems to be wrong, If its not an MST then we dont want to read remote.
this should be something like:
seq_puts(m, "\tHDCP version: ");
if (intel_encoder_is_mst(encoder)) {
intel_hdcp_info(m, intel_connector, true);
seq_puts(m, "\tMST Hub HDCP version: ");
intel_hdcp_info(m, intel_connector, false);
}
else {
intel_hdcp_info(m, intel_connector, false);
}
Regards,
Ankit
> +
> + if (intel_encoder_is_mst(encoder)) {
> + seq_puts(m, "\tMST Hub HDCP version: ");
> + intel_hdcp_info(m, intel_connector, false);
> + }
>
> seq_printf(m, "\tmax bpc: %u\n", connector->display_info.bpc);
>
> @@ -1131,7 +1142,12 @@ static int i915_hdcp_sink_capability_show(struct seq_file *m, void *data)
>
> seq_printf(m, "%s:%d HDCP version: ", connector->base.name,
> connector->base.base.id);
> - intel_hdcp_info(m, connector);
> + intel_hdcp_info(m, connector, true);
> +
> + if (intel_encoder_is_mst(connector->encoder)) {
> + seq_puts(m, "\tMST Hub HDCP version: ");
> + intel_hdcp_info(m, connector, false);
> + }
>
> out:
> drm_modeset_unlock(&i915->drm.mode_config.connection_mutex);
next prev parent reply other threads:[~2024-02-02 9:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 6:38 [PATCH 00/11] HDCP Type1 MST fixes Suraj Kandpal
2024-02-02 6:38 ` [PATCH 01/11] drm/i915/hdcp: Move to direct reads for HDCP Suraj Kandpal
2024-02-02 6:38 ` [PATCH 02/11] drm/i915/hdcp: Move source hdcp2 checks into its own function Suraj Kandpal
2024-02-02 6:38 ` [PATCH 03/11] drm/i915/hdcp: Refactor intel_dp_hdcp2_capable Suraj Kandpal
2024-02-02 6:38 ` [PATCH 04/11] drm/i915/hdcp: Pass drm_dp_aux to read_bcaps function Suraj Kandpal
2024-02-02 6:38 ` [PATCH 05/11] drm/i915/hdcp: Add new remote capability check shim function Suraj Kandpal
2024-02-02 10:01 ` Nautiyal, Ankit K
2024-02-02 6:38 ` [PATCH 06/11] drm/i915/hdcp: HDCP Capability for the downstream device Suraj Kandpal
2024-02-02 9:56 ` Nautiyal, Ankit K [this message]
2024-02-02 6:38 ` [PATCH 07/11] drm/i915/hdcp: Remove additional timing for reading mst hdcp message Suraj Kandpal
2024-02-02 6:38 ` [PATCH 08/11] drm/i915/hdcp: Extract hdcp structure from correct connector Suraj Kandpal
2024-02-02 6:38 ` [PATCH 09/11] drm/i915/hdcp: Save acquire_ctx in intel_hdcp Suraj Kandpal
2024-02-02 6:38 ` [PATCH 10/11] drm/i915/hdcp: Allocate stream id after HDCP AKE stage Suraj Kandpal
2024-02-02 6:38 ` [PATCH 11/11] drm/i915/hdcp: Read Rxcaps for robustibility Suraj Kandpal
2024-02-02 7:20 ` ✗ Fi.CI.SPARSE: warning for HDCP Type1 MST fixes Patchwork
2024-02-02 7:39 ` ✗ Fi.CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-02-04 7:39 [PATCH 00/11] " Suraj Kandpal
2024-02-04 7:39 ` [PATCH 06/11] drm/i915/hdcp: HDCP Capability for the downstream device Suraj Kandpal
2024-02-04 14:24 [PATCH 00/11] HDCP Type1 MST fixes Suraj Kandpal
2024-02-04 14:25 ` [PATCH 06/11] drm/i915/hdcp: HDCP Capability for the downstream device Suraj Kandpal
2024-02-07 5:31 ` Nautiyal, Ankit K
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=6fc619ad-96dd-4c45-8728-73f726fa555c@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=suraj.kandpal@intel.com \
--cc=uma.shankar@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