From: sashiko-bot@kernel.org
To: "George Karagounis" <taterraster@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/display: Replace bw_constrained with max_link_bpp_x16
Date: Mon, 21 Sep 2026 07:10:06 +0000 [thread overview]
Message-ID: <20260921071006.9B6FD1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260919161927.98829-1-mail@taterr.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] drm/i915/display: incomplete cleanup of bw_constrained flag
--
commit f4c7087cb31d33cb453437886f7788a5ffe134a2
Author: George Karagounis <taterraster@gmail.com>
drm/i915/display: Replace bw_constrained with max_link_bpp_x16
This commit replaces the legacy bw_constrained boolean flag checks with
direct comparisons against the max_link_bpp_x16 fixed-point API in both
intel_crt.c and intel_lvds.c.
> diff --git a/drivers/gpu/drm/i915/display/intel_lvds.c b/drivers/gpu/drm/i915/display/intel_lvds.c
> index 872753478cf21..6bbd13ab5da7b 100644
> --- a/drivers/gpu/drm/i915/display/intel_lvds.c
> +++ b/drivers/gpu/drm/i915/display/intel_lvds.c
[ ... ]
> @@ -443,10 +443,10 @@ static int intel_lvds_compute_config(struct intel_atomic_state *state,
> else
> lvds_bpp = 6*3;
>
> - /* TODO: Check crtc_state->max_link_bpp_x16 instead of bw_constrained */
> - if (lvds_bpp != crtc_state->pipe_bpp && !crtc_state->bw_constrained) {
> + if (lvds_bpp != crtc_state->pipe_bpp &&
> + crtc_state->max_link_bpp_x16 >= fxp_q4_from_int(lvds_bpp)) {
[Severity: Low]
Does this commit intentionally leave the bw_constrained flag definition and
other writes intact?
While this patch removes the readers of bw_constrained, the flag remains
defined in struct intel_crtc_state:
drivers/gpu/drm/i915/display/intel_display_types.h:struct intel_crtc_state {
...
bool bw_constrained;
...
}
It also still appears to be stored whenever crtc_state->pipe_bpp >
fxp_q4_to_int(crtc_state->max_link_bpp_x16) during mode setting:
drivers/gpu/drm/i915/display/intel_display.c:intel_modeset_pipe_config() {
...
crtc_state->bw_constrained = true;
...
}
Because the readers were removed, this causes unnecessary code complexity and
leaves behind a dead store. Is there a plan to remove the flag entirely, or
was this an oversight?
> drm_dbg_kms(display->drm,
> - "forcing display bpp (was %d) to LVDS (%d)\n",
> + "forcing display bpp (was %d) to LVDS (%d)\n",
> crtc_state->pipe_bpp, lvds_bpp);
> crtc_state->pipe_bpp = lvds_bpp;
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260919161927.98829-1-mail@taterr.org?part=1
next prev parent reply other threads:[~2026-09-21 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 16:19 [PATCH] drm/i915/display: Replace bw_constrained with max_link_bpp_x16 George Karagounis
2026-09-21 7:10 ` sashiko-bot [this message]
2026-09-21 16:48 ` ✗ LGCI.VerificationFailed: failure for " Patchwork
2026-09-24 16:49 ` [PATCH v2] " George Karagounis
2026-09-25 20:58 ` ✗ LGCI.VerificationFailed: failure for drm/i915/display: Replace bw_constrained with max_link_bpp_x16 (rev2) 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=20260921071006.9B6FD1F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=taterraster@gmail.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