Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dp_mst: Disable DSC on ICL+ MST outputs
Date: Thu, 2 Nov 2023 16:06:44 +0200	[thread overview]
Message-ID: <ZUOsb4D0qi6Oq0oB@intel.com> (raw)
In-Reply-To: <20231102115935.2591979-1-imre.deak@intel.com>

On Thu, Nov 02, 2023 at 01:59:35PM +0200, Imre Deak wrote:
> Enabling DSC on ICL MST outputs is broken leading to FIFO pipe /
> transcoder underruns and blank screen. On TGL+ platforms MST/DSC works -
> after fixing the known issues in [1] - however to make this work on ICL
> requires more work.
> 
> So far DSC on MST probably didn't get enabled for users - due to an issue
> fixed by [2] - but after fixing that, DSC could get enabled, leading to a
> blank screen in ICL/MST configurations which do work atm. To prevent
> this disable MST/DSC on ICL for now.
> 
> [1] https://lore.kernel.org/all/20231030155843.2251023-1-imre.deak@intel.com
> [2] https://lore.kernel.org/all/20231030155843.2251023-31-imre.deak@intel.com
> 
> Cc: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_dp_mst.c | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> index 82f425ef15953..2cd3bccc0e650 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> @@ -43,6 +43,7 @@
>  #include "intel_dpio_phy.h"
>  #include "intel_hdcp.h"
>  #include "intel_hotplug.h"
> +#include "intel_vdsc.h"
>  #include "skl_scaler.h"
>  
>  static int intel_dp_mst_check_constraints(struct drm_i915_private *i915, int bpp,
> @@ -297,6 +298,14 @@ static int intel_dp_mst_update_slots(struct intel_encoder *encoder,
>  	return 0;
>  }
>  
> +static bool
> +intel_dp_mst_dsc_source_support(const struct intel_crtc_state *crtc_state)
> +{
> +	struct drm_i915_private *i915 = to_i915(crtc_state->uapi.crtc->dev);
> +
> +	return DISPLAY_VER(i915) > 11 && intel_dsc_source_support(crtc_state);

We typically say >=12 not >11. Also please include a small comment to
explaing why icl is excluded so people don't have to wonder what's going
on here.

Apart from that
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> +}
> +
>  static bool
>  intel_dp_mst_compute_config_limits(struct intel_dp *intel_dp,
>  				   struct intel_crtc_state *crtc_state,
> @@ -375,6 +384,9 @@ static int intel_dp_mst_compute_config(struct intel_encoder *encoder,
>  			    str_yes_no(ret),
>  			    str_yes_no(intel_dp->force_dsc_en));
>  
> +		if (!intel_dp_mst_dsc_source_support(pipe_config))
> +			return -EINVAL;
> +
>  		if (!intel_dp_mst_compute_config_limits(intel_dp,
>  							pipe_config,
>  							true,
> -- 
> 2.39.2

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2023-11-02 14:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 11:59 [Intel-gfx] [PATCH] drm/i915/dp_mst: Disable DSC on ICL+ MST outputs Imre Deak
2023-11-02 14:06 ` Ville Syrjälä [this message]
2023-11-02 19:44 ` [Intel-gfx] [PATCH v2] " Imre Deak
2023-11-03  7:42 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dp_mst: Disable DSC on ICL+ MST outputs (rev2) Patchwork
2023-11-03  8:01 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-03 21:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dp_mst: Disable DSC on ICL+ MST outputs (rev3) Patchwork
2023-11-03 21:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-04 13:50 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-06 11:45   ` Imre Deak
2023-11-07 18:16     ` Illipilli, TejasreeX
2023-11-07 13:56 ` Patchwork
2023-11-07 17:35 ` Patchwork
2023-11-07 17:41 ` Patchwork
2023-11-07 17:57 ` Patchwork
2023-11-07 18:12 ` [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=ZUOsb4D0qi6Oq0oB@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=imre.deak@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