From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 2/4] drm/i915/fbc: Fix nuke for pre-snb platforms
Date: Fri, 3 Jul 2020 14:45:38 +0300 [thread overview]
Message-ID: <20200703114538.GM6112@intel.com> (raw)
In-Reply-To: <4640b96482ac43decad11d006ca7112433b742ed.camel@intel.com>
On Thu, Jul 02, 2020 at 11:02:05PM +0000, Souza, Jose wrote:
> On Thu, 2020-07-02 at 18:37 +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > The MSG_FBC_REND_STATE register only exists on snb+. For older
> > platforms (would also work for snb+) we can simply rewite DSPSURF
> > to trigger a flip nuke.
> >
> > While generally RMW is considered harmful we'll use it here for
> > simplicity. And since FBC doesn't exist in i830 we don't have to
> > worry about the DSPSURF double buffering hardware fails present
> > on that platform.
>
> Did not found a explicit statement about writing DSPSURF will nuke compressed buffer but that makes sense,
Flip nuke is certainly a thing, but flipping to the same address I think
might be somewhat undefined. IIRC I did test this however and it worked
just fine.
> also checked that MSG_FBC_REND_STATE do not
> exist this older platforms.
>
> Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
>
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_fbc.c | 34 +++++++++++++++++++++++-
> > 1 file changed, 33 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c b/drivers/gpu/drm/i915/display/intel_fbc.c
> > index d30c2a389294..036546ce8db8 100644
> > --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> > +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> > @@ -187,8 +187,30 @@ static bool g4x_fbc_is_active(struct drm_i915_private *dev_priv)
> > return intel_de_read(dev_priv, DPFC_CONTROL) & DPFC_CTL_EN;
> > }
> >
> > +static void i8xx_fbc_recompress(struct drm_i915_private *dev_priv)
> > +{
> > + struct intel_fbc_reg_params *params = &dev_priv->fbc.params;
> > + enum i9xx_plane_id i9xx_plane = params->crtc.i9xx_plane;
> > +
> > + spin_lock_irq(&dev_priv->uncore.lock);
> > + intel_de_write_fw(dev_priv, DSPADDR(i9xx_plane),
> > + intel_de_read_fw(dev_priv, DSPADDR(i9xx_plane)));
> > + spin_unlock_irq(&dev_priv->uncore.lock);
> > +}
> > +
> > +static void i965_fbc_recompress(struct drm_i915_private *dev_priv)
> > +{
> > + struct intel_fbc_reg_params *params = &dev_priv->fbc.params;
> > + enum i9xx_plane_id i9xx_plane = params->crtc.i9xx_plane;
> > +
> > + spin_lock_irq(&dev_priv->uncore.lock);
> > + intel_de_write_fw(dev_priv, DSPSURF(i9xx_plane),
> > + intel_de_read_fw(dev_priv, DSPSURF(i9xx_plane)));
> > + spin_unlock_irq(&dev_priv->uncore.lock);
> > +}
> > +
> > /* This function forces a CFB recompression through the nuke operation. */
> > -static void intel_fbc_recompress(struct drm_i915_private *dev_priv)
> > +static void snb_fbc_recompress(struct drm_i915_private *dev_priv)
> > {
> > struct intel_fbc *fbc = &dev_priv->fbc;
> >
> > @@ -198,6 +220,16 @@ static void intel_fbc_recompress(struct drm_i915_private *dev_priv)
> > intel_de_posting_read(dev_priv, MSG_FBC_REND_STATE);
> > }
> >
> > +static void intel_fbc_recompress(struct drm_i915_private *dev_priv)
> > +{
> > + if (INTEL_GEN(dev_priv) >= 6)
> > + snb_fbc_recompress(dev_priv);
> > + else if (INTEL_GEN(dev_priv) >= 4)
> > + i965_fbc_recompress(dev_priv);
> > + else
> > + i8xx_fbc_recompress(dev_priv);
> > +}
> > +
> > static void ilk_fbc_activate(struct drm_i915_private *dev_priv)
> > {
> > struct intel_fbc_reg_params *params = &dev_priv->fbc.params;
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-07-03 11:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 15:37 [Intel-gfx] [PATCH 0/4] drm/i915: FBC fixes Ville Syrjala
2020-07-02 15:37 ` [Intel-gfx] [PATCH 1/4] drm/i915/fbc: Use the correct plane stride Ville Syrjala
2020-07-02 23:24 ` Souza, Jose
2020-07-03 11:38 ` Ville Syrjälä
2020-07-06 20:53 ` Souza, Jose
2020-07-07 12:24 ` Ville Syrjälä
2020-07-07 0:37 ` Rodrigo Vivi
2020-07-02 15:37 ` [Intel-gfx] [PATCH 2/4] drm/i915/fbc: Fix nuke for pre-snb platforms Ville Syrjala
2020-07-02 23:02 ` Souza, Jose
2020-07-03 11:45 ` Ville Syrjälä [this message]
2020-07-02 15:37 ` [Intel-gfx] [PATCH 3/4] drm/i915/fbc: Enable fbc on i865 Ville Syrjala
2020-07-02 22:06 ` Souza, Jose
2020-07-02 15:37 ` [Intel-gfx] [PATCH 4/4] drm/i915/fbc: Allow FBC to recompress after a 3D workload on i85x/i865 Ville Syrjala
2020-07-02 22:22 ` Souza, Jose
2020-07-02 16:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: FBC fixes (rev3) Patchwork
2020-07-02 22:02 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20200703114538.GM6112@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.