From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Write zero wms if we disable planes for icl+
Date: Wed, 18 May 2022 15:05:44 +0300 [thread overview]
Message-ID: <20220518120544.GA28397@intel.com> (raw)
In-Reply-To: <87ee0rdq01.fsf@intel.com>
On Wed, May 18, 2022 at 02:44:30PM +0300, Jani Nikula wrote:
> On Wed, 18 May 2022, Stanislav Lisovskiy <stanislav.lisovskiy@intel.com> wrote:
> > Otherwise we seem to get FIFO underruns. It is being disabled
> > anyway, so kind of logical to write those as zeroes, even if
> > disabling is temporary.
> >
> > Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> > ---
> > .../drm/i915/display/skl_universal_plane.c | 2 +-
> > drivers/gpu/drm/i915/intel_pm.c | 46 +++++++++++++++++++
> > drivers/gpu/drm/i915/intel_pm.h | 2 +
> > 3 files changed, 49 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/skl_universal_plane.c b/drivers/gpu/drm/i915/display/skl_universal_plane.c
> > index caa03324a733..c0251189c042 100644
> > --- a/drivers/gpu/drm/i915/display/skl_universal_plane.c
> > +++ b/drivers/gpu/drm/i915/display/skl_universal_plane.c
> > @@ -633,7 +633,7 @@ icl_plane_disable_arm(struct intel_plane *plane,
> > if (icl_is_hdr_plane(dev_priv, plane_id))
> > intel_de_write_fw(dev_priv, PLANE_CUS_CTL(pipe, plane_id), 0);
> >
> > - skl_write_plane_wm(plane, crtc_state);
> > + skl_write_zero_plane_wm(plane, crtc_state);
> >
> > intel_psr2_disable_plane_sel_fetch(plane, crtc_state);
> > intel_de_write_fw(dev_priv, PLANE_CTL(pipe, plane_id), 0);
> > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > index ee0047fdc95d..2470c037bfae 100644
> > --- a/drivers/gpu/drm/i915/intel_pm.c
> > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > @@ -5885,6 +5885,52 @@ void skl_write_plane_wm(struct intel_plane *plane,
> > PLANE_NV12_BUF_CFG(pipe, plane_id), ddb_y);
> > }
> >
> > +void skl_write_zero_plane_wm(struct intel_plane *plane,
> > + const struct intel_crtc_state *crtc_state)
> > +{
> > + struct drm_i915_private *dev_priv = to_i915(plane->base.dev);
> > + int level, max_level = ilk_wm_max_level(dev_priv);
> > + enum plane_id plane_id = plane->id;
> > + enum pipe pipe = plane->pipe;
> > + struct skl_pipe_wm pipe_wm;
> > + const struct skl_ddb_entry *ddb =
> > + &crtc_state->wm.skl.plane_ddb[plane_id];
> > + const struct skl_ddb_entry *ddb_y =
> > + &crtc_state->wm.skl.plane_ddb_y[plane_id];
> > +
> > + for (level = 0; level <= max_level; level++) {
>
> Not your doing here, but why have we adopted this error prone inclusive
> max that always makes you take a double look in the for loops?!
>
> BR,
> Jani.
No clue, really. It seems to be used same way all over the place in
intel_pm.c. I was suggesting there is some smart reasoning behind this,
so simply follow the common approach.
For me it is more confusing that apparently it is called "ilk_*" which
is IronLake probably, however we use it everywhere.
I would call it simple i915_wm_max_level and make it determine itself based on
dev_priv which platform it is..
Stan
>
> > + pipe_wm.planes[plane_id].wm[level].blocks = 0;
> > + pipe_wm.planes[plane_id].wm[level].lines = 0;
> > + }
> > +
> > + pipe_wm.planes[plane_id].trans_wm.blocks = 0;
> > + pipe_wm.planes[plane_id].trans_wm.lines = 0;
> > +
> > + for (level = 0; level <= max_level; level++)
> > + skl_write_wm_level(dev_priv, PLANE_WM(pipe, plane_id, level),
> > + skl_plane_wm_level(&pipe_wm, plane_id, level));
> > +
> > + skl_write_wm_level(dev_priv, PLANE_WM_TRANS(pipe, plane_id),
> > + skl_plane_trans_wm(&pipe_wm, plane_id));
> > +
> > + if (HAS_HW_SAGV_WM(dev_priv)) {
> > + const struct skl_plane_wm *wm = &pipe_wm.planes[plane_id];
> > +
> > + skl_write_wm_level(dev_priv, PLANE_WM_SAGV(pipe, plane_id),
> > + &wm->sagv.wm0);
> > + skl_write_wm_level(dev_priv, PLANE_WM_SAGV_TRANS(pipe, plane_id),
> > + &wm->sagv.trans_wm);
> > + }
> > +
> > + skl_ddb_entry_write(dev_priv,
> > + PLANE_BUF_CFG(pipe, plane_id), ddb);
> > +
> > + if (DISPLAY_VER(dev_priv) < 11)
> > + skl_ddb_entry_write(dev_priv,
> > + PLANE_NV12_BUF_CFG(pipe, plane_id), ddb_y);
> > +}
> > +
> > +
> > void skl_write_cursor_wm(struct intel_plane *plane,
> > const struct intel_crtc_state *crtc_state)
> > {
> > diff --git a/drivers/gpu/drm/i915/intel_pm.h b/drivers/gpu/drm/i915/intel_pm.h
> > index 50604cf7398c..fb0ac4f143ab 100644
> > --- a/drivers/gpu/drm/i915/intel_pm.h
> > +++ b/drivers/gpu/drm/i915/intel_pm.h
> > @@ -61,6 +61,8 @@ bool skl_wm_level_equals(const struct skl_wm_level *l1,
> > bool skl_ddb_allocation_overlaps(const struct skl_ddb_entry *ddb,
> > const struct skl_ddb_entry *entries,
> > int num_entries, int ignore_idx);
> > +void skl_write_zero_plane_wm(struct intel_plane *plane,
> > + const struct intel_crtc_state *crtc_state);
> > void skl_write_plane_wm(struct intel_plane *plane,
> > const struct intel_crtc_state *crtc_state);
> > void skl_write_cursor_wm(struct intel_plane *plane,
>
> --
> Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-05-18 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 10:59 [Intel-gfx] [PATCH] drm/i915: Write zero wms if we disable planes for icl+ Stanislav Lisovskiy
2022-05-18 11:25 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-05-18 11:25 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-05-18 11:44 ` [Intel-gfx] [PATCH] " Jani Nikula
2022-05-18 12:05 ` Lisovskiy, Stanislav [this message]
2022-05-18 13:02 ` Ville Syrjälä
2022-05-18 11:51 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2022-05-23 8:06 ` [Intel-gfx] [PATCH] " Govindapillai, Vinod
2022-05-23 8:31 ` Lisovskiy, Stanislav
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=20220518120544.GA28397@intel.com \
--to=stanislav.lisovskiy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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