intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org, suraj.kandpal@intel.com,
	imre.deak@intel.com
Subject: Re: [PATCH 02/14] drm/i915/dp: Return early if DSC not supported
Date: Tue, 17 Dec 2024 12:55:09 +0200	[thread overview]
Message-ID: <871py6sho2.fsf@intel.com> (raw)
In-Reply-To: <20241217093244.3938132-3-ankit.k.nautiyal@intel.com>

On Tue, 17 Dec 2024, Ankit Nautiyal <ankit.k.nautiyal@intel.com> wrote:
> Check for DSC support before computing link config with DSC.
> For DP MST we are already doing the same.
>
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Reviewed-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_dp.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 908b9887f89b..dd2da9facaad 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -2375,9 +2375,6 @@ int intel_dp_dsc_compute_config(struct intel_dp *intel_dp,
>  		 intel_dp_supports_fec(intel_dp, connector, pipe_config) &&
>  		 !intel_dp_is_uhbr(pipe_config));
>  
> -	if (!intel_dp_supports_dsc(intel_dp, connector, pipe_config))
> -		return -EINVAL;
> -
>  	if (!intel_dp_dsc_supports_format(connector, pipe_config->output_format))
>  		return -EINVAL;
>  
> @@ -2652,6 +2649,9 @@ intel_dp_compute_link_config(struct intel_encoder *encoder,
>  			    str_yes_no(ret), str_yes_no(joiner_needs_dsc),
>  			    str_yes_no(intel_dp->force_dsc_en));
>  
> +		if (!intel_dp_supports_dsc(intel_dp, connector, pipe_config))
> +			return -EINVAL;
> +

The (pre-existing) problem with this is that we debug log we fall back
to DSC, while we don't.

Maybe we should do something like this instead, both in SST and MST code:

--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -2644,6 +2644,11 @@ intel_dp_compute_link_config(struct intel_encoder *encoder,
 			dsc_needed = true;
 	}
 
+	if (dsc_needed && !intel_dp_supports_dsc(connector, pipe_config)) {
+		drm_dbg_kms(display->drm, "DSC required but not available.\n");
+		return -EINVAL;
+	}
+
 	if (dsc_needed) {
 		drm_dbg_kms(display->drm,
 			    "Try DSC (fallback=%s, joiner=%s, force=%s)\n",

BR,
Jani.

>  		if (!intel_dp_compute_config_limits(intel_dp, pipe_config,
>  						    respect_downstream_limits,
>  						    true,

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-12-17 10:55 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17  9:32 [PATCH 00/14] DP DSC min/max src bpc fixes Ankit Nautiyal
2024-12-17  9:32 ` [PATCH 01/14] drm/i915/dp: Refactor FEC support check in intel_dp_supports_dsc Ankit Nautiyal
2024-12-17 10:43   ` Jani Nikula
2024-12-17  9:32 ` [PATCH 02/14] drm/i915/dp: Return early if DSC not supported Ankit Nautiyal
2024-12-17 10:55   ` Jani Nikula [this message]
2024-12-17 11:02     ` Jani Nikula
2024-12-24 10:08       ` Nautiyal, Ankit K
2024-12-17  9:32 ` [PATCH 03/14] drm/i915/dp: Separate out helper for compute fec_enable Ankit Nautiyal
2024-12-17 10:57   ` Jani Nikula
2024-12-17  9:32 ` [PATCH 04/14] drm/i915/dp: Drop check for FEC in intel_dp_fec_compute_config Ankit Nautiyal
2024-12-17 10:57   ` Jani Nikula
2024-12-17  9:32 ` [PATCH 05/14] drm/i915/dp: Remove HAS_DSC macro for intel_dp_dsc_max_src_input_bpc Ankit Nautiyal
2024-12-17  9:32 ` [PATCH 06/14] drm/i915/dp: Return int from dsc_max/min_src_input_bpc helpers Ankit Nautiyal
2024-12-17  9:32 ` [PATCH 07/14] drm/i915/dp_mst: Use helpers to get dsc min/max input bpc Ankit Nautiyal
2024-12-17  9:32 ` [PATCH 08/14] drm/i915/dp: Drop max_requested_bpc for dsc pipe_min/max bpp Ankit Nautiyal
2024-12-17  9:32 ` [PATCH 09/14] drm/i915/dp: Refactor pipe_bpp limits with dsc Ankit Nautiyal
2024-12-17  9:32 ` [PATCH 10/14] drm/i915/dp_mst: Use pipe_bpp->limits.{max/min}_bpp for dsc Ankit Nautiyal
2024-12-18  4:06   ` Kandpal, Suraj
2024-12-17  9:32 ` [PATCH 11/14] drm/i915/dp: Use clamp for pipe_bpp limits with DSC Ankit Nautiyal
2024-12-17  9:32 ` [PATCH 12/14] drm/i915/dp: Make dsc helpers accept const crtc_state pointers Ankit Nautiyal
2024-12-17  9:32 ` [PATCH 13/14] drm/i915/dp: Set the DSC link limits in intel_dp_compute_config_link_bpp_limits Ankit Nautiyal
2024-12-17  9:32 ` [PATCH 14/14] drm/i915/dp_mst: Use link.{min/max}_bpp_x16 Ankit Nautiyal
2024-12-18  4:06   ` Kandpal, Suraj
2024-12-17 12:28 ` ✗ Fi.CI.SPARSE: warning for DP DSC min/max src bpc fixes (rev11) Patchwork
2024-12-17 12:41 ` ✓ i915.CI.BAT: success " Patchwork
2024-12-17 19:19 ` ✗ i915.CI.Full: failure " Patchwork
2024-12-18 16:58 ` ✓ i915.CI.Full: success " Patchwork
2024-12-24 10:11 ` [PATCH 00/14] DP DSC min/max src bpc fixes Nautiyal, Ankit K
  -- strict thread matches above, loose matches on Subject: below --
2024-12-04  9:26 Ankit Nautiyal
2024-12-04  9:26 ` [PATCH 02/14] drm/i915/dp: Return early if DSC not supported Ankit Nautiyal

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=871py6sho2.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@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;
as well as URLs for NNTP newsgroup(s).