Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v4 4/4] drm/i915/hdcp: Fill hdcp2_streamid_type and k in appropriate places
Date: Mon, 15 May 2023 16:52:54 +0530	[thread overview]
Message-ID: <fbd73085-f892-cfd5-6e02-42ddd410d568@intel.com> (raw)
In-Reply-To: <20230515103225.688830-5-suraj.kandpal@intel.com>


On 5/15/2023 4:02 PM, Suraj Kandpal wrote:
> stream_id and k(no of streams) should be set in
> intel_hdcp_set_content_streams. stream_type should be set in
> intel_hdcp_required_content_stream.
>
> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
>   drivers/gpu/drm/i915/display/intel_hdcp.c | 9 +++------
>   1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c b/drivers/gpu/drm/i915/display/intel_hdcp.c
> index 6c3cd3b7db69..350ca3ba5fc8 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdcp.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
> @@ -97,7 +97,6 @@ static void intel_hdcp_prepare_streams(struct intel_connector *connector)
>   	struct intel_hdcp *hdcp = &connector->hdcp;
>   
>   	if (!intel_encoder_is_mst(intel_attached_encoder(connector))) {
> -		data->k = 1;
>   		data->streams[0].stream_type = hdcp->content_type;
>   	} else {
>   		intel_hdcp_required_content_stream(dig_port);
> @@ -2159,7 +2158,6 @@ static int initialize_hdcp_port_data(struct intel_connector *connector,
>   {
>   	struct drm_i915_private *dev_priv = to_i915(connector->base.dev);
>   	struct hdcp_port_data *data = &dig_port->hdcp_port_data;
> -	struct intel_hdcp *hdcp = &connector->hdcp;
>   	enum port port = dig_port->base.port;
>   
>   	if (DISPLAY_VER(dev_priv) < 12)
> @@ -2189,9 +2187,6 @@ static int initialize_hdcp_port_data(struct intel_connector *connector,
>   		drm_err(&dev_priv->drm, "Out of Memory\n");
>   		return -ENOMEM;
>   	}
> -	/* For SST */
> -	data->streams[0].stream_id = 0;
> -	data->streams[0].stream_type = hdcp->content_type;
>   
>   	return 0;
>   }
> @@ -2297,8 +2292,10 @@ intel_hdcp_set_streams(struct intel_digital_port *dig_port,
>   	struct drm_i915_private *i915 = to_i915(dig_port->base.base.dev);
>   	struct hdcp_port_data *data = &dig_port->hdcp_port_data;
>   
> -	if (!intel_encoder_is_mst(&dig_port->base))
> +	if (!intel_encoder_is_mst(&dig_port->base)) {
> +		data->k = 1;

setting data->streams[0].stream_id = 0; is missing from the last patch.

Regards,

Ankit

>   		return 0;
> +	}
>   
>   	data->k = 0;
>   

  reply	other threads:[~2023-05-15 11:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 10:32 [Intel-gfx] [PATCH v4 0/4] Fix modeset locking issue in HDCP MST Suraj Kandpal
2023-05-15 10:32 ` [Intel-gfx] [PATCH v4 1/4] drm/i915/hdcp: add intel_atomic_state argument to hdcp_enable function Suraj Kandpal
2023-05-15 10:32 ` [Intel-gfx] [PATCH v4 2/4] drm/i915/hdcp: Remove enforce_type0 check outside loop Suraj Kandpal
2023-05-15 10:32 ` [Intel-gfx] [PATCH v4 3/4] drm/i915/hdcp: Fix modeset locking issue in hdcp mst Suraj Kandpal
2023-05-15 11:20   ` Nautiyal, Ankit K
2023-05-15 10:32 ` [Intel-gfx] [PATCH v4 4/4] drm/i915/hdcp: Fill hdcp2_streamid_type and k in appropriate places Suraj Kandpal
2023-05-15 11:22   ` Nautiyal, Ankit K [this message]
2023-05-15 11:27   ` [Intel-gfx] [PATCH v5 " Suraj Kandpal
2023-05-15 22:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Fix modeset locking issue in HDCP MST (rev5) Patchwork
2023-05-15 22:51 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-05-16  7:32 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-16  7:38 ` Patchwork
2023-05-16  9:44 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-05-16  9:59 ` Patchwork
2023-05-16 11:37 ` [Intel-gfx] [PATCH v4 0/4] Fix modeset locking issue in HDCP MST Manna, Animesh

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=fbd73085-f892-cfd5-6e02-42ddd410d568@intel.com \
    --to=ankit.k.nautiyal@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