public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: Imre Deak <imre.deak@intel.com>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Cc: <stable@vger.kernel.org>, Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Subject: Re: [PATCH v2 1/2] drm/i915/dp: Fix pipe BPP clamping due to HDR
Date: Mon, 9 Feb 2026 19:58:32 +0530	[thread overview]
Message-ID: <baa6c5c6-5adb-4cf5-9d01-ad8d2c37db1d@intel.com> (raw)
In-Reply-To: <20260209133817.395823-1-imre.deak@intel.com>



On 2/9/2026 7:08 PM, Imre Deak wrote:
> The pipe BPP value shouldn't be set outside of the source's / sink's
> valid pipe BPP range, ensure this when increasing the minimum pipe BPP
> value to 30 due to HDR.
> 
> While at it debug print if the HDR mode was requested for a connector by
> setting the corresponding HDR connector property. This indicates
> if the requested HDR mode could not be enabled, since the selected
> pipe BPP is below 30, due to a sink capability or link BW limit.
> 
> v2:
> - Also handle the case where the sink could support the target 30 BPP
>    only in DSC mode due to a BW limit, but the sink doesn't support DSC
>    or 30 BPP as a DSC input BPP. (Chaitanya)
> - Debug print the connector's HDR mode in the link config dump, to
>    indicate if a BPP >= 30 required by HDR couldn't be reached. (Ankit)
> - Add Closes: trailer. (Ankit)
> - Don't print the 30 BPP-outside of valid BPP range debug message if
>    the min BPP is already > 30 (and so a target BPP >= 30 required
>    for HDR is ensured).

Does this match the current implementation?

> 
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/7052

Also,
Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15503

> Fixes: ba49a4643cf53 ("drm/i915/dp: Set min_bpp limit to 30 in HDR mode")
> Cc: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
> Cc: <stable@vger.kernel.org> # v6.18+
> Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com> # v1
> Signed-off-by: Imre Deak <imre.deak@intel.com>
> ---
>   drivers/gpu/drm/i915/display/intel_dp.c | 20 +++++++++++++++++---
>   1 file changed, 17 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 4b786706ea2de..7fd20df10f26f 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -2703,6 +2703,7 @@ intel_dp_compute_config_limits(struct intel_dp *intel_dp,
>   			       bool dsc,
>   			       struct link_config_limits *limits)
>   {
> +	struct intel_display *display = to_intel_display(intel_dp);
>   	bool is_mst = intel_crtc_has_type(crtc_state, INTEL_OUTPUT_DP_MST);
>   	struct intel_connector *connector =
>   		to_intel_connector(conn_state->connector);
> @@ -2715,8 +2716,7 @@ intel_dp_compute_config_limits(struct intel_dp *intel_dp,
>   	limits->min_lane_count = intel_dp_min_lane_count(intel_dp);
>   	limits->max_lane_count = intel_dp_max_lane_count(intel_dp);
>   
> -	limits->pipe.min_bpp = intel_dp_in_hdr_mode(conn_state) ? 30 :
> -				intel_dp_min_bpp(crtc_state->output_format);
> +	limits->pipe.min_bpp = intel_dp_min_bpp(crtc_state->output_format);
>   	if (is_mst) {
>   		/*
>   		 * FIXME: If all the streams can't fit into the link with their
> @@ -2732,6 +2732,19 @@ intel_dp_compute_config_limits(struct intel_dp *intel_dp,
>   							respect_downstream_limits);
>   	}
>   
> +	if (!dsc && intel_dp_in_hdr_mode(conn_state)) {
> +		if (intel_dp_supports_dsc(intel_dp, connector, crtc_state) &&
> +		    limits->pipe.max_bpp >= 30)
> +			limits->pipe.min_bpp = max(limits->pipe.min_bpp, 30);
> +		else
> +			drm_dbg_kms(display->drm,
> +				    "[CONNECTOR:%d:%s] Can't force 30 bpp for HDR (pipe bpp: %d-%d DSC-support: %s)\n",
> +				    connector->base.base.id, connector->base.name,
> +				    limits->pipe.min_bpp, limits->pipe.max_bpp,
> +				    str_yes_no(intel_dp_supports_dsc(intel_dp, connector,
> +								     crtc_state)));
> +	}
> +

Nit: We could collect the output of intel_dp_supports_dsc() in a variable.

But not a blocker.

Reviewed-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>

>   	if (dsc && !intel_dp_dsc_compute_pipe_bpp_limits(connector, limits))
>   		return false;
>   
> @@ -2869,10 +2882,11 @@ intel_dp_compute_link_for_joined_pipes(struct intel_encoder *encoder,
>   	}
>   
>   	drm_dbg_kms(display->drm,
> -		    "DP lane count %d clock %d bpp input %d compressed " FXP_Q4_FMT " link rate required %d available %d\n",
> +		    "DP lane count %d clock %d bpp input %d compressed " FXP_Q4_FMT " HDR %s link rate required %d available %d\n",
>   		    pipe_config->lane_count, pipe_config->port_clock,
>   		    pipe_config->pipe_bpp,
>   		    FXP_Q4_ARGS(pipe_config->dsc.compressed_bpp_x16),
> +		    str_yes_no(intel_dp_in_hdr_mode(conn_state)),
>   		    intel_dp_config_required_rate(pipe_config),
>   		    intel_dp_max_link_data_rate(intel_dp,
>   						pipe_config->port_clock,


  parent reply	other threads:[~2026-02-09 14:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09 13:38 [PATCH v2 1/2] drm/i915/dp: Fix pipe BPP clamping due to HDR Imre Deak
2026-02-09 13:38 ` [PATCH v2 2/2] drm/i915/dp: Verify valid pipe BPP range Imre Deak
2026-02-09 13:44 ` ✓ CI.KUnit: success for series starting with [v2,1/2] drm/i915/dp: Fix pipe BPP clamping due to HDR Patchwork
2026-02-09 14:18 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-09 14:28 ` Borah, Chaitanya Kumar [this message]
2026-02-09 15:40   ` [PATCH v2 1/2] " Imre Deak
2026-02-10  6:14     ` Borah, Chaitanya Kumar
2026-02-09 17:17 ` ✗ Xe.CI.FULL: failure for series starting with [v2,1/2] " Patchwork
     [not found] ` <177067695572.239579.15984876432204423723@a3b018990fe9>
2026-02-10  9:55   ` ✗ i915.CI.Full: " Imre Deak

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=baa6c5c6-5adb-4cf5-9d01-ad8d2c37db1d@intel.com \
    --to=chaitanya.kumar.borah@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=stable@vger.kernel.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