From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Deak, Imre" <imre.deak@intel.com>
Subject: Re: [PATCH] drm/i915/dp: Simplify intel_dp_needs_8b10b_fec()
Date: Tue, 21 Oct 2025 04:29:28 +0000 [thread overview]
Message-ID: <6117e1b424e66faae0f9dc3713dea16ed0257e6f.camel@intel.com> (raw)
In-Reply-To: <20251020154438.416761-1-imre.deak@intel.com>
On Mon, 2025-10-20 at 18:44 +0300, Imre Deak wrote:
> The intel_crtc_state::fec_enable check in intel_dp_needs_8b10b_fec()
> is
> redundant drop it: originally it ensured that the FEC enabled state
> for
> a CRTC other than the CRTC intel_dp_needs_8b10b_fec() called for is
> preserved, even if DSC is not enabled for the latter CRTC. The way
> FEC
> gets enabled for all the CRTCs on an 8b10b MST link is changed by
>
> commit 7c027070e98d ("drm/i915/dp_mst: Track DSC enabled status on
> the
> MST link") and
> commit 470b84af457e ("drm/i915/dp_mst: Recompute all MST link CRTCs
> if
> DSC gets enabled on the link")
>
> depending on intel_dsc_enabled_on_link() in
> intel_dp_needs_8b10b_fec()
> instead of the above fec_enable check. Drop the check.
>
> Suggested-by: Jouni Högander <jouni.hogander@intel.com>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
Reviewed-by: Jouni Högander <jouni.hogander@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c
> b/drivers/gpu/drm/i915/display/intel_dp.c
> index b0aeb6c2de86c..475518b4048b7 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -2377,9 +2377,6 @@ bool intel_dp_needs_8b10b_fec(const struct
> intel_crtc_state *crtc_state,
> if (intel_dp_is_uhbr(crtc_state))
> return false;
>
> - if (crtc_state->fec_enable)
> - return true;
> -
> /*
> * Though eDP v1.5 supports FEC with DSC, unlike DP, it is
> optional.
> * Since, FEC is a bandwidth overhead, continue to not
> enable it for
prev parent reply other threads:[~2025-10-21 4:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 15:44 [PATCH] drm/i915/dp: Simplify intel_dp_needs_8b10b_fec() Imre Deak
2025-10-20 20:57 ` ✓ CI.KUnit: success for " Patchwork
2025-10-21 0:00 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-21 2:41 ` ✗ Xe.CI.Full: failure " Patchwork
2025-10-21 4:29 ` Hogander, Jouni [this message]
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=6117e1b424e66faae0f9dc3713dea16ed0257e6f.camel@intel.com \
--to=jouni.hogander@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