From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 2/7] drm/i915/psr: Stop using intel_dsc_enabled_on_link to detect crtc DSC status
Date: Tue, 9 Jun 2026 17:44:05 +0530 [thread overview]
Message-ID: <52f74617-93ff-417c-a48d-4a2c58262e1f@intel.com> (raw)
In-Reply-To: <20260608141124.144878-3-jouni.hogander@intel.com>
On 6/8/2026 7:41 PM, Jouni Högander wrote:
> Intel_dsc_enabled_on_link is not really about DSC being enabled on crtc. It
> is telling if FEC is enabled on link.
Hmm... This is a bit unclear to me.
As per commit 470b84af457e ("drm/i915/dp_mst: Recompute all MST link
CRTCs if DSC gets enabled on the link")
We wanted to do away with FEC tracking, and instead tracked DSC. FEC for
UHBR was not getting filled so it makes sense to track DSC (FEC being
mandatory for DP DSC).
From commit message for commit 470b84af457e
"...
Based on the above, to be able to determine the DSC state on both
non-UHBR and UHBR MST links, track the more generic DSC-enabled-on-link
state (instead of the FEC-enabled-on-link state) for each CRTC in
intel_link_bw_limits."
So to me it appears that we were actually concerned about DSC and not
FEC and started using intel_dsc_enabled_on_link()
(later, fec_enable was unused and removed).
Perhaps I am missing some context?
> Instead of intel_dsc_enabled_on_link
> check status directly from crtc->dsc.compression_enable.
I agree to this part though. We can separate it out in any case.
Regards,
Ankit
>
> Also rename intel_dsc_enabled_on_link as intel_fec_enabled_on_link.
>
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_psr.c | 6 +++---
> drivers/gpu/drm/i915/display/intel_vdsc.c | 2 +-
> drivers/gpu/drm/i915/display/intel_vdsc.h | 2 +-
> 3 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
> index ad2f6c79f5808..f58200d38ac2c 100644
> --- a/drivers/gpu/drm/i915/display/intel_psr.c
> +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> @@ -1740,7 +1740,7 @@ static bool intel_sel_update_config_valid(struct intel_crtc_state *crtc_state,
> if (!connector->dp.panel_replay_caps.su_support)
> goto unsupported;
>
> - if (intel_dsc_enabled_on_link(crtc_state) &&
> + if (crtc_state->dsc.compression_enable &&
> connector->dp.panel_replay_caps.dsc_support !=
> INTEL_DP_PANEL_REPLAY_DSC_SELECTIVE_UPDATE) {
> drm_dbg_kms(display->drm,
> @@ -1840,7 +1840,7 @@ static bool _panel_replay_compute_config(struct intel_crtc_state *crtc_state,
> return false;
> }
>
> - if (intel_dsc_enabled_on_link(crtc_state) &&
> + if (crtc_state->dsc.compression_enable &&
> connector->dp.panel_replay_caps.dsc_support ==
> INTEL_DP_PANEL_REPLAY_DSC_NOT_SUPPORTED) {
> drm_dbg_kms(display->drm,
> @@ -3235,7 +3235,7 @@ verify_panel_replay_dsc_state(const struct intel_crtc_state *crtc_state)
> return;
>
> drm_WARN_ON(display->drm,
> - intel_dsc_enabled_on_link(crtc_state) &&
> + crtc_state->dsc.compression_enable &&
> crtc_state->panel_replay_dsc_support ==
> INTEL_DP_PANEL_REPLAY_DSC_NOT_SUPPORTED);
> }
> diff --git a/drivers/gpu/drm/i915/display/intel_vdsc.c b/drivers/gpu/drm/i915/display/intel_vdsc.c
> index 8f06c3a4d56df..35c93fcbb6427 100644
> --- a/drivers/gpu/drm/i915/display/intel_vdsc.c
> +++ b/drivers/gpu/drm/i915/display/intel_vdsc.c
> @@ -431,7 +431,7 @@ void intel_dsc_enable_on_crtc(struct intel_crtc_state *crtc_state)
> crtc_state->dsc.compression_enable = true;
> }
>
> -bool intel_dsc_enabled_on_link(const struct intel_crtc_state *crtc_state)
> +bool intel_fec_enabled_on_link(const struct intel_crtc_state *crtc_state)
> {
> struct intel_display *display = to_intel_display(crtc_state);
>
> diff --git a/drivers/gpu/drm/i915/display/intel_vdsc.h b/drivers/gpu/drm/i915/display/intel_vdsc.h
> index 3372f8694054d..60d86399808c0 100644
> --- a/drivers/gpu/drm/i915/display/intel_vdsc.h
> +++ b/drivers/gpu/drm/i915/display/intel_vdsc.h
> @@ -28,7 +28,7 @@ void intel_dsc_enable(const struct intel_crtc_state *crtc_state);
> void intel_dsc_disable(const struct intel_crtc_state *crtc_state);
> int intel_dsc_compute_params(struct intel_crtc_state *pipe_config);
> void intel_dsc_enable_on_crtc(struct intel_crtc_state *crtc_state);
> -bool intel_dsc_enabled_on_link(const struct intel_crtc_state *crtc_state);
> +bool intel_fec_enabled_on_link(const struct intel_crtc_state *crtc_state);
> void intel_dsc_get_config(struct intel_crtc_state *crtc_state);
> enum intel_display_power_domain
> intel_dsc_power_domain(struct intel_crtc *crtc, enum transcoder cpu_transcoder);
next prev parent reply other threads:[~2026-06-09 12:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 14:11 [PATCH 0/7] Enable FEC when using DP Panel Replay Jouni Högander
2026-06-08 14:11 ` [PATCH 1/7] drm/i915/psr: Check FEC support for " Jouni Högander
2026-06-09 11:29 ` Nautiyal, Ankit K
2026-06-08 14:11 ` [PATCH 2/7] drm/i915/psr: Stop using intel_dsc_enabled_on_link to detect crtc DSC status Jouni Högander
2026-06-09 12:14 ` Nautiyal, Ankit K [this message]
2026-06-09 13:30 ` Hogander, Jouni
2026-06-09 13:45 ` Imre Deak
2026-06-18 6:04 ` Hogander, Jouni
2026-06-08 14:11 ` [PATCH 3/7] drm/i915/display: Rename compression_enabled_on_link and link_dsc_pipes Jouni Högander
2026-06-08 14:11 ` [PATCH 4/7] drm/i915/psr: Split PSR compute config Jouni Högander
2026-06-08 14:11 ` [PATCH 5/7] drm/i915/psr: Move DP/eDP Panel Replay compute config to pre " Jouni Högander
2026-06-08 14:11 ` [PATCH 6/7] drm/i915/psr: Add PSR specific " Jouni Högander
2026-06-08 14:11 ` [PATCH 7/7] drm/i915/psr: Enable FEC if using DP Panel Replay Jouni Högander
2026-06-08 20:37 ` ✓ i915.CI.BAT: success for Enable FEC when " Patchwork
2026-06-09 1:44 ` ✗ i915.CI.Full: failure " 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=52f74617-93ff-417c-a48d-4a2c58262e1f@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jouni.hogander@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox