From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Imre Deak <imre.deak@intel.com>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>
Cc: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>,
<stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] drm/i915/dp: Fix pipe BPP clamping due to HDR
Date: Fri, 6 Feb 2026 19:20:02 +0530 [thread overview]
Message-ID: <f6b59555-01f6-49ff-aff4-a6da9d347332@intel.com> (raw)
In-Reply-To: <20260206104227.290231-1-imre.deak@intel.com>
On 2/6/2026 4:12 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.
>
> 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+
> Signed-off-by: Imre Deak <imre.deak@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 2b8f43e211741..4d8f480cf803f 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -2697,6 +2697,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);
> @@ -2709,8 +2710,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
> @@ -2726,6 +2726,16 @@ intel_dp_compute_config_limits(struct intel_dp *intel_dp,
> respect_downstream_limits);
> }
>
> + if (intel_dp_in_hdr_mode(conn_state)) {
> + if (limits->pipe.min_bpp <= 30 && limits->pipe.max_bpp >= 30)
> + limits->pipe.min_bpp = 30;
> + else
> + drm_dbg_kms(display->drm,
> + "[CONNECTOR:%d:%s] HDR min 30 bpp outside of valid pipe bpp range (%d-%d)\n",
> + connector->base.base.id, connector->base.name,
> + limits->pipe.min_bpp, limits->pipe.max_bpp);
pipe.max_bpp < 30 will be either due to the max_bpc property set to less
than 10, or perhaps when the panel itself does not support 10 bpc
(limited by EDID or VBT).
With these constraints doesn't make sense to enable HDR and send HDR
metadata.
However, as we see in some reported issues [1] [2], in practice some
compositor seems to enable HDR by default and with the hard limit set,
they report blankout.
So it does make sense to raise the min bpp limit only if its inside the
supported range.
Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
[1] https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/7052
[2]
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5969#note_3248404
> + }
> +
> if (dsc && !intel_dp_dsc_compute_pipe_bpp_limits(connector, limits))
> return false;
>
next prev parent reply other threads:[~2026-02-06 13:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 10:42 [PATCH 1/2] drm/i915/dp: Fix pipe BPP clamping due to HDR Imre Deak
2026-02-06 10:42 ` [PATCH 2/2] drm/i915/dp: Verify valid pipe BPP range Imre Deak
2026-02-06 13:52 ` Nautiyal, Ankit K
2026-02-06 10:49 ` ✓ CI.KUnit: success for series starting with [1/2] drm/i915/dp: Fix pipe BPP clamping due to HDR Patchwork
2026-02-06 11:25 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-06 13:50 ` Nautiyal, Ankit K [this message]
2026-02-09 6:36 ` [PATCH 1/2] " Borah, Chaitanya Kumar
2026-02-09 8:40 ` Imre Deak
2026-02-09 9:25 ` Borah, Chaitanya Kumar
2026-02-09 9:34 ` Imre Deak
2026-02-09 10:09 ` Imre Deak
2026-02-09 11:30 ` Nautiyal, Ankit K
2026-02-09 11:54 ` Imre Deak
2026-02-09 12:45 ` Nautiyal, Ankit K
2026-02-09 13:08 ` Imre Deak
2026-02-09 11:49 ` Borah, Chaitanya Kumar
2026-02-07 12:10 ` ✗ Xe.CI.FULL: failure for series starting with [1/2] " 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=f6b59555-01f6-49ff-aff4-a6da9d347332@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=chaitanya.kumar.borah@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