From: "Michał Grzelak" <michal.grzelak@intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
jouni.hogander@intel.com, ville.syrjala@linux.intel.com,
animesh.manna@intel.com
Subject: Re: [PATCH 1/5] drm/i915/alpm: Compute LOBF late after guardband is already determined
Date: Thu, 20 Nov 2025 09:51:42 +0100 (CET) [thread overview]
Message-ID: <f7c6986f-12b8-240c-f49e-1503e5a47c05@intel.com> (raw)
In-Reply-To: <20251119135152.673276-2-ankit.k.nautiyal@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
Hi Ankit,
On Wed, 19 Nov 2025, Ankit Nautiyal wrote:
> Currently intel_alpm_lobf_compute_config() tries to account for
> guardband +SCL requirements during encoder->compute_config() phase,
> even before guardband is computed.
> Also, LOBF depends on crtc_state->has_psr which can be modified in
> encoder->compute_config_late().
>
> Account for lobf requirements while optimizing the guardband and add
> checks for final guardband in encoder->compute_config_late() phase after
> the guardband and the final state of crtc_state->has_psr are already
> computed.
>
> Use crtc_state->vrr.guardband and crtc_state->set_context_latency for
> the computation and add more documentation for the dependency of first
> sdp position, guardband, set context latency and wake lines.
>
> v2: Add helper to use min guardband required for lobf.
>
> Bspec:71041
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_alpm.c | 63 +++++++++++++++++-----
> drivers/gpu/drm/i915/display/intel_alpm.h | 3 ++
> drivers/gpu/drm/i915/display/intel_dp.c | 2 +
> drivers/gpu/drm/i915/display/intel_intel.c | 0
>
> [...]
>
> diff --git a/drivers/gpu/drm/i915/display/intel_intel.c b/drivers/gpu/drm/i915/display/intel_intel.c
> new file mode 100644
> index 000000000000..e69de29bb2d1
Nitpick, but it looks like an empty file named intel_intel.c stepped
into the patch, which is also seen in the above shortlog. Otherwise,
Reviewed-by: Michał Grzelak <michal.grzelak@intel.com>
BR,
Michał
next prev parent reply other threads:[~2025-11-20 8:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 13:51 [PATCH 0/5] LOBF fixes Ankit Nautiyal
2025-11-19 13:51 ` [PATCH 1/5] drm/i915/alpm: Compute LOBF late after guardband is already determined Ankit Nautiyal
2025-11-20 8:51 ` Michał Grzelak [this message]
2025-11-20 12:21 ` Nautiyal, Ankit K
2025-11-19 13:51 ` [PATCH 2/5] drm/i915/alpm: Allow LOBF only if window1 > alpm check_entry lines Ankit Nautiyal
2025-11-20 8:52 ` Michał Grzelak
2025-11-19 13:51 ` [PATCH 3/5] drm/i915/alpm: Allow LOBF only for platform that have Always on VRR TG Ankit Nautiyal
2025-11-20 8:52 ` Michał Grzelak
2025-11-19 13:51 ` [PATCH 4/5] drm/i915/alpm: Simplify and align LOBF checks in pre/post plane update Ankit Nautiyal
2025-11-20 8:52 ` Michał Grzelak
2025-11-19 13:51 ` [PATCH 5/5] drm/i915/alpm: Disable LOBF around transitioning for LRR/seamless MN Ankit Nautiyal
2025-11-20 8:53 ` Michał Grzelak
2025-11-19 14:09 ` ✗ CI.checkpatch: warning for LOBF fixes (rev2) Patchwork
2025-11-19 14:11 ` ✓ CI.KUnit: success " Patchwork
2025-11-19 14:26 ` ✗ CI.checksparse: warning " Patchwork
2025-11-19 15:11 ` ✓ Xe.CI.BAT: success " Patchwork
2025-11-19 17:26 ` ✗ Xe.CI.Full: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-11-14 5:27 [PATCH 0/5] LOBF fixes Ankit Nautiyal
2025-11-14 5:27 ` [PATCH 1/5] drm/i915/alpm: Compute LOBF late after guardband is already determined Ankit Nautiyal
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=f7c6986f-12b8-240c-f49e-1503e5a47c05@intel.com \
--to=michal.grzelak@intel.com \
--cc=animesh.manna@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jouni.hogander@intel.com \
--cc=ville.syrjala@linux.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;
as well as URLs for NNTP newsgroup(s).