From: Imre Deak <imre.deak@intel.com>
To: Khaled Almahallawy <khaled.almahallawy@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
Jani Nikula <jani.nikula@intel.com>,
Charlton Lin <charlton.lin@intel.com>
Subject: Re: [PATCH v2 1/2] drm/i915/dp: Enable SST LT fallback between UHBR and non-UHBR link rates
Date: Mon, 7 Apr 2025 10:04:32 +0300 [thread overview]
Message-ID: <Z_N5AAOf9uVeXPUV@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <20250405003434.641638-1-khaled.almahallawy@intel.com>
On Fri, Apr 04, 2025 at 05:34:33PM -0700, Khaled Almahallawy wrote:
> With all the pieces for UHBR SST LT implemented, we can now enable LT
> fallback switching between SST UHBR and non-UHBR link rates.
>
> [...]
>
> @@ -1303,7 +1233,7 @@ static int intel_dp_get_link_train_fallback_values(struct intel_dp *intel_dp,
> return 0;
> }
>
> - if (!reduce_link_params(intel_dp, crtc_state, &new_link_rate, &new_lane_count))
> + if (!reduce_link_params_in_bw_order(intel_dp, crtc_state, &new_link_rate, &new_lane_count))
On SST - during state computation - a minimum link configuration
required for the mode was selected to beging with. Simply reducing that
link config further in BW order as for MST (which selected the maximum
link config to begin with) doesn't work.
> return -1;
>
> if (intel_dp_is_edp(intel_dp) &&
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-04-07 7:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 0:34 [PATCH v2 1/2] drm/i915/dp: Enable SST LT fallback between UHBR and non-UHBR link rates Khaled Almahallawy
2025-04-05 0:34 ` [PATCH v2 2/2] drm/i915/dp: Handle LT fallback modes when sink/lttpr changes supported config Khaled Almahallawy
2025-04-07 7:18 ` Imre Deak
2025-04-05 1:23 ` ✓ i915.CI.BAT: success for series starting with [v2,1/2] drm/i915/dp: Enable SST LT fallback between UHBR and non-UHBR link rates Patchwork
2025-04-05 4:00 ` ✗ i915.CI.Full: failure " Patchwork
2025-04-07 7:04 ` Imre Deak [this message]
2025-04-07 20:41 ` [PATCH v2 1/2] " Almahallawy, Khaled
2025-04-07 21:41 ` 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=Z_N5AAOf9uVeXPUV@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=charlton.lin@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=khaled.almahallawy@intel.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 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.