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>
Subject: Re: [PATCH 2/2] drm/i915/dp: Verify valid pipe BPP range
Date: Fri, 6 Feb 2026 19:22:50 +0530 [thread overview]
Message-ID: <9912112c-3414-4778-92eb-e89ae25b48b2@intel.com> (raw)
In-Reply-To: <20260206104227.290231-2-imre.deak@intel.com>
On 2/6/2026 4:12 PM, Imre Deak wrote:
> Ensure that the pipe BPP range is valid after calculating the minimum
> and maximum pipe BPP values separately.
>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index 4d8f480cf803f..720787e86ff17 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -2736,6 +2736,15 @@ intel_dp_compute_config_limits(struct intel_dp *intel_dp,
> limits->pipe.min_bpp, limits->pipe.max_bpp);
> }
>
> + if (limits->pipe.min_bpp <= 0 ||
> + limits->pipe.min_bpp > limits->pipe.max_bpp) {
> + drm_dbg_kms(display->drm, "[CONNECTOR:%d:%s] Invalid pipe bpp range: %d-%d\n",
> + connector->base.base.id, connector->base.name,
> + limits->pipe.min_bpp, limits->pipe.max_bpp);
> +
> + return false;
> + }
> +
> if (dsc && !intel_dp_dsc_compute_pipe_bpp_limits(connector, limits))
> return false;
>
next prev parent reply other threads:[~2026-02-06 13:53 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 [this message]
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 ` [PATCH 1/2] " Nautiyal, Ankit K
2026-02-09 6:36 ` 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=9912112c-3414-4778-92eb-e89ae25b48b2@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@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