From: Jani Nikula <jani.nikula@intel.com>
To: Animesh Manna <animesh.manna@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jouni.hogander@intel.com, jeevan.b@intel.com,
Animesh Manna <animesh.manna@intel.com>
Subject: Re: [PATCH v8 6/9] drm/i915/lobf: Update lobf if any change in dependent parameters
Date: Thu, 08 May 2025 14:57:10 +0300 [thread overview]
Message-ID: <87frhftiw9.fsf@intel.com> (raw)
In-Reply-To: <20250409140258.785834-7-animesh.manna@intel.com>
On Wed, 09 Apr 2025, Animesh Manna <animesh.manna@intel.com> wrote:
> For every commit the dependent condition for LOBF is checked
> and accordingly update has_lobf flag which will be used
> to update the ALPM_CTL register during commit.
>
> v1: Initial version.
> v2: Avoid reading h/w register without has_lobf check. [Jani]
> v3: Update LOBF in post plane update instead of separate function. [Jouni]
> v4:
> - Add lobf disable print. [Jouni]
> - Simplify condition check for enabling/disabling lobf. [Jouni]
>
> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_alpm.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_alpm.c b/drivers/gpu/drm/i915/display/intel_alpm.c
> index 01949b90c0c3..4fe1914ff759 100644
> --- a/drivers/gpu/drm/i915/display/intel_alpm.c
> +++ b/drivers/gpu/drm/i915/display/intel_alpm.c
> @@ -362,6 +362,8 @@ static void lnl_alpm_configure(struct intel_dp *intel_dp,
> if (crtc_state->has_lobf) {
> alpm_ctl |= ALPM_CTL_LOBF_ENABLE;
> drm_dbg_kms(display->drm, "Link off between frames (LOBF) enabled\n");
> + } else {
> + drm_dbg_kms(display->drm, "Link off between frames (LOBF) disabled\n");
> }
Maybe just one line?
drm_dbg_kms(display->drm, "Link off between frames (LOBF) %s\n",
str_enabled_disabled(crtc_state->has_lobf));
>
> alpm_ctl |= ALPM_CTL_ALPM_ENTRY_CHECK(intel_dp->alpm_parameters.check_entry_lines);
> @@ -382,9 +384,12 @@ void intel_alpm_post_plane_update(struct intel_atomic_state *state,
> struct intel_display *display = to_intel_display(state);
> const struct intel_crtc_state *crtc_state =
> intel_atomic_get_new_crtc_state(state, crtc);
> + const struct intel_crtc_state *old_crtc_state =
> + intel_atomic_get_old_crtc_state(state, crtc);
> struct intel_encoder *encoder;
>
> - if (!crtc_state->has_lobf && !crtc_state->has_psr)
> + if (crtc_state->has_lobf == old_crtc_state->has_lobf &&
> + !crtc_state->has_psr)
> return;
>
> for_each_intel_encoder_mask(display->drm, encoder,
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-05-08 11:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 14:02 [PATCH v8 0/9] LOBF enablement fix Animesh Manna
2025-04-09 14:02 ` [PATCH v8 1/9] drm/i915/alpm: use variable from intel_crtc_state instead of intel_psr Animesh Manna
2025-04-09 14:02 ` [PATCH v8 2/9] drm/i915/lobf: Add lobf enablement in post plane update Animesh Manna
2025-04-09 14:02 ` [PATCH v8 3/9] drm/i915/lobf: Add debug print for LOBF Animesh Manna
2025-04-09 14:02 ` [PATCH v8 4/9] drm/i915/lobf: Disintegrate alpm_disable from psr_disable Animesh Manna
2025-04-09 14:02 ` [PATCH v8 5/9] drm/i915/lobf: Add fixed refresh rate check in compute_config() Animesh Manna
2025-04-09 14:02 ` [PATCH v8 6/9] drm/i915/lobf: Update lobf if any change in dependent parameters Animesh Manna
2025-04-15 5:40 ` Hogander, Jouni
2025-05-08 11:57 ` Jani Nikula [this message]
2025-04-09 14:02 ` [PATCH v8 7/9] drm/i915/lobf: Add debug interface for lobf Animesh Manna
2025-04-15 5:54 ` Hogander, Jouni
2025-04-09 14:02 ` [PATCH v8 8/9] drm/i915/lobf: Add mutex for alpm update Animesh Manna
2025-04-09 14:02 ` [PATCH v8 9/9] drm/i915/lobf: Check for sink error and disable LOBF Animesh Manna
2025-04-09 16:46 ` ✗ Fi.CI.CHECKPATCH: warning for LOBF enablement fix (rev8) Patchwork
2025-04-09 17:11 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-10 1:21 ` ✗ i915.CI.Full: failure " Patchwork
2025-04-15 5:24 ` [PATCH v8 0/9] LOBF enablement fix Hogander, Jouni
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=87frhftiw9.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=animesh.manna@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jeevan.b@intel.com \
--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