From: tarund18303@gmail.com
To: jani.nikula@linux.intel.com
Cc: rodrigo.vivi@intel.com, joonas.lahtinen@linux.intel.com,
tursulin@ursulin.net, airlied@gmail.com, simona@ffwll.ch,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
tarun-tarun143 <tarund18303@gmail.com>
Subject: [PATCH] drm/i915/dp_link_caps: Validate max link rate
Date: Thu, 27 Aug 2026 02:20:34 +0000 [thread overview]
Message-ID: <20260827022035.3442-1-tarund18303@gmail.com> (raw)
From: tarun-tarun143 <tarund18303@gmail.com>
Validate the maximum link rate against the source-supported rates
before using the maximum link limits to calculate allowed
configurations.
This prevents an unsupported link rate from being accepted as a
maximum link limit.
Signed-off-by: tarun-tarun143 <tarund18303@gmail.com>
---
drivers/gpu/drm/i915/display/intel_dp_link_caps.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_dp_link_caps.c b/drivers/gpu/drm/i915/display/intel_dp_link_caps.c
index 7b6cc6055da8..0934488153bb 100644
--- a/drivers/gpu/drm/i915/display/intel_dp_link_caps.c
+++ b/drivers/gpu/drm/i915/display/intel_dp_link_caps.c
@@ -710,7 +710,10 @@ static bool max_link_limits_valid(struct intel_dp_link_caps *link_caps,
!is_power_of_2(max_link_limits->lane_count))
return false;
- /* TODO: Validate max_link_limits->rate against the source supported rates. */
+ if (intel_dp_rate_index(link_caps->dp->source_rates,
+ link_caps->dp->num_source_rates,
+ max_link_limits->rate) < 0)
+ return false;
intel_dp_link_caps_get_forced_params(link_caps, &forced_params);
allowed_configs = calc_allowed_config_filter(link_caps, link_caps->enabled_configs,
base-commit: 73e3f0710014fe6d4ed98cfc02292f6121db7558
--
2.43.0
next reply other threads:[~2026-08-27 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 2:20 tarund18303 [this message]
2026-08-27 2:33 ` [PATCH] drm/i915/dp_link_caps: Validate max link rate sashiko-bot
2026-08-27 12:30 ` ✗ LGCI.VerificationFailed: failure for " Patchwork
2026-08-27 12:39 ` Patchwork
2026-09-09 12:16 ` [PATCH] " Jani Nikula
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=20260827022035.3442-1-tarund18303@gmail.com \
--to=tarund18303@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.