From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Manna, Animesh" <animesh.manna@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Nikula, Jani" <jani.nikula@intel.com>, "B, Jeevan" <jeevan.b@intel.com>
Subject: Re: [PATCH v6 4/8] drm/i915/lobf: Update lobf if any change in dependent parameters
Date: Thu, 27 Mar 2025 11:00:41 +0000 [thread overview]
Message-ID: <d6259af76c4c20f54a72908f7d0c5bd406e070eb.camel@intel.com> (raw)
In-Reply-To: <MW4SPRMB005674D7F917AB6187A44156F9A12@MW4SPRMB0056.namprd11.prod.outlook.com>
On Thu, 2025-03-27 at 10:43 +0000, Manna, Animesh wrote:
>
>
> > -----Original Message-----
> > From: Hogander, Jouni <jouni.hogander@intel.com>
> > Sent: Monday, March 24, 2025 1:36 PM
> > To: intel-xe@lists.freedesktop.org; Manna, Animesh
> > <animesh.manna@intel.com>; intel-gfx@lists.freedesktop.org
> > Cc: Nikula, Jani <jani.nikula@intel.com>; B, Jeevan
> > <jeevan.b@intel.com>
> > Subject: Re: [PATCH v6 4/8] drm/i915/lobf: Update lobf if any
> > change in
> > dependent parameters
> >
> > On Thu, 2025-03-20 at 00:45 +0530, Animesh Manna 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]
> > >
> > > Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> > > ---
> > > drivers/gpu/drm/i915/display/intel_alpm.c | 5 ++++-
> > > 1 file changed, 4 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/gpu/drm/i915/display/intel_alpm.c
> > > b/drivers/gpu/drm/i915/display/intel_alpm.c
> > > index c2862888466f..5df1253a6b6c 100644
> > > --- a/drivers/gpu/drm/i915/display/intel_alpm.c
> > > +++ b/drivers/gpu/drm/i915/display/intel_alpm.c
> > > @@ -378,9 +378,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 && !crtc_state->has_psr &&
> > > + !old_crtc_state->has_lobf)
> >
> > I don't really understand this change? Where lobf is disabled when
> > has_lobf
> > is false?
>
> When crtc_state->has_lobf = false and old_crtc_state->has_lobf =
> true,
> then (!crtc_state->has_lobf && !crtc_state->has_psr &&
> !old_crtc_state->has_lobf) = false, so return will not happen.
Ok, I see. How about crtc_state->has_lobf = true and old_crtc_state-
>has_lobf = true. Do you still want to configure it? How about
crtc_state->has_lobf != old_crtc_state->has_lobf?
> Next lnl_alpm_configure() will program other aux-wake/aux-less alpm
> related bits except lobf-enable. Do you see any issue here?
I think it should be. Thank you for the clarification.
BR,
Jouni Högander
>
> Regards,
> Animesh
> >
> > BR,
> >
> > Jouni Högander
> > > return;
> > >
> > > for_each_intel_encoder_mask(display->drm, encoder,
>
next prev parent reply other threads:[~2025-03-27 11:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 19:15 [PATCH v6 0/8] LOBF enablement fix Animesh Manna
2025-03-19 19:15 ` [PATCH v6 1/8] drm/i915/lobf: Add lobf enablement in post plane update Animesh Manna
2025-03-24 7:59 ` Hogander, Jouni
2025-03-19 19:15 ` [PATCH v6 2/8] drm/i915/lobf: Disintegrate alpm_disable from psr_disable Animesh Manna
2025-03-19 19:15 ` [PATCH v6 3/8] drm/i915/lobf: Add fixed refresh rate check in compute_config() Animesh Manna
2025-03-24 8:00 ` Hogander, Jouni
2025-03-19 19:15 ` [PATCH v6 4/8] drm/i915/lobf: Update lobf if any change in dependent parameters Animesh Manna
2025-03-24 8:05 ` Hogander, Jouni
2025-03-27 10:43 ` Manna, Animesh
2025-03-27 11:00 ` Hogander, Jouni [this message]
2025-03-19 19:15 ` [PATCH v6 5/8] drm/i915/lobf: Add debug interface for lobf Animesh Manna
2025-03-24 8:07 ` Hogander, Jouni
2025-03-27 10:44 ` Manna, Animesh
2025-03-24 8:35 ` Jani Nikula
2025-03-19 19:15 ` [PATCH v6 6/8] drm/i915/lobf: Check for sink error and disable LOBF Animesh Manna
2025-03-24 7:53 ` Hogander, Jouni
2025-03-27 10:54 ` Manna, Animesh
2025-03-19 19:15 ` [PATCH v6 7/8] drm/i915/lobf: Add mutex for alpm update Animesh Manna
2025-03-24 7:56 ` Hogander, Jouni
2025-03-19 19:15 ` [PATCH v6 8/8] drm/i915/lobf: Add debug print for LOBF Animesh Manna
2025-03-24 7:59 ` Hogander, Jouni
2025-03-27 10:55 ` Manna, Animesh
2025-03-19 19:42 ` ✓ CI.Patch_applied: success for LOBF enablement fix (rev5) Patchwork
2025-03-19 19:42 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-19 19:43 ` ✓ CI.KUnit: success " Patchwork
2025-03-19 20:00 ` ✓ CI.Build: " Patchwork
2025-03-19 20:02 ` ✓ CI.Hooks: " Patchwork
2025-03-19 20:03 ` ✗ CI.checksparse: warning " Patchwork
2025-03-19 20:25 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-19 21:21 ` ✗ Xe.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=d6259af76c4c20f54a72908f7d0c5bd406e070eb.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=animesh.manna@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jeevan.b@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