From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: WA: FBC Render Nuke.
Date: Thu, 23 May 2013 12:48:45 +0300 [thread overview]
Message-ID: <20130523094845.GB5004@intel.com> (raw)
In-Reply-To: <1369243397-2819-1-git-send-email-rodrigo.vivi@gmail.com>
On Wed, May 22, 2013 at 02:23:17PM -0300, Rodrigo Vivi wrote:
> According BSPec: "Workaround: Do not enable Render Command Streamer tracking for FBC.
> Instead insert a LRI to address 0x50380 with data 0x00000004 after the PIPE_CONTROL that
> follows each render submission."
>
> v2: Chris noticed that flush_domains check was missing here and also suggested to do
> LRI only when fbc is enabled. To avoid do a I915_READ on every flush lets use the
> module parameter check.
>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@gmail.com>
> ---
> drivers/gpu/drm/i915/i915_reg.h | 2 ++
> drivers/gpu/drm/i915/intel_pm.c | 2 +-
> drivers/gpu/drm/i915/intel_ringbuffer.c | 32 ++++++++++++++++++++++++++++++++
> 3 files changed, 35 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index cc4c223..81ac584 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -977,6 +977,8 @@
> /* Framebuffer compression for Ivybridge */
> #define IVB_FBC_RT_BASE 0x7020
>
> +#define MSG_FBC_REND_STATE 0x50380
> +#define FBC_REND_NUKE (1<<2)
>
> #define _HSW_PIPE_SLICE_CHICKEN_1_A 0x420B0
> #define _HSW_PIPE_SLICE_CHICKEN_1_B 0x420B4
> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> index 1879188..e830a9b 100644
> --- a/drivers/gpu/drm/i915/intel_pm.c
> +++ b/drivers/gpu/drm/i915/intel_pm.c
> @@ -274,7 +274,7 @@ static void gen7_enable_fbc(struct drm_crtc *crtc, unsigned long interval)
> struct drm_i915_gem_object *obj = intel_fb->obj;
> struct intel_crtc *intel_crtc = to_intel_crtc(crtc);
>
> - I915_WRITE(IVB_FBC_RT_BASE, obj->gtt_offset | ILK_FBC_RT_VALID);
> + I915_WRITE(IVB_FBC_RT_BASE, obj->gtt_offset);
>
> if (!intel_edp_is_psr_enabled(dev))
> I915_WRITE(ILK_DPFC_CONTROL, DPFC_CTL_EN | DPFC_CTL_LIMIT_1X |
> diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> index 3d2c236..905d372 100644
> --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> @@ -280,6 +280,30 @@ gen7_render_ring_cs_stall_wa(struct intel_ring_buffer *ring)
> return 0;
> }
>
> +static int gen7_ring_fbc_flush(struct intel_ring_buffer *ring)
> +{
> + struct drm_device *dev = ring->dev;
> + int ret;
> +
> + if (i915_enable_fbc == 0)
> + return 0;
> +
> + if (i915_enable_fbc < 0 && !IS_HASWELL(dev))
> + return 0;
> +
> + ret = intel_ring_begin(ring, 4);
> + if (ret)
> + return ret;
> +
> + intel_ring_emit(ring, MI_NOOP);
> + intel_ring_emit(ring, MI_LOAD_REGISTER_IMM(1));
> + intel_ring_emit(ring, MSG_FBC_REND_STATE);
> + intel_ring_emit(ring, FBC_REND_NUKE);
> + intel_ring_advance(ring);
According to the PM enabling guide you should do a SRM from the same
register after the LRI. Is that not required?
> +
> + return 0;
> +}
> +
> static int
> gen7_render_ring_flush(struct intel_ring_buffer *ring,
> u32 invalidate_domains, u32 flush_domains)
> @@ -336,6 +360,9 @@ gen7_render_ring_flush(struct intel_ring_buffer *ring,
> intel_ring_emit(ring, 0);
> intel_ring_advance(ring);
>
> + if (flush_domains)
> + return gen7_ring_fbc_flush(ring);
> +
> return 0;
> }
>
> @@ -1623,6 +1650,7 @@ gen6_ring_dispatch_execbuffer(struct intel_ring_buffer *ring,
> static int blt_ring_flush(struct intel_ring_buffer *ring,
> u32 invalidate, u32 flush)
> {
> + struct drm_device *dev = ring->dev;
> uint32_t cmd;
> int ret;
>
> @@ -1645,6 +1673,10 @@ static int blt_ring_flush(struct intel_ring_buffer *ring,
> intel_ring_emit(ring, 0);
> intel_ring_emit(ring, MI_NOOP);
> intel_ring_advance(ring);
> +
> + if (IS_GEN7(dev))
> + return gen7_ring_fbc_flush(ring);
> +
> return 0;
> }
>
> --
> 1.8.1.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-05-23 9:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 17:23 [PATCH] drm/i915: WA: FBC Render Nuke Rodrigo Vivi
2013-05-23 9:48 ` Ville Syrjälä [this message]
2013-05-23 10:28 ` Damien Lespiau
2013-05-23 18:06 ` Rodrigo Vivi
2013-05-24 8:13 ` Ville Syrjälä
2013-05-23 10:30 ` [PATCH] drm/i915: Track when we dirty the scanout with render commands Chris Wilson
-- strict thread matches above, loose matches on Subject: below --
2013-06-06 19:53 [PATCH 2/2] drm/i915: WA: FBC Render Nuke Rodrigo Vivi
2013-06-06 19:58 ` [PATCH] " Rodrigo Vivi
2013-06-07 15:58 ` Daniel Vetter
2013-05-29 0:25 Rodrigo Vivi
2013-05-29 0:36 ` Rodrigo Vivi
2013-05-31 15:59 ` Ville Syrjälä
2013-05-31 20:15 ` Rodrigo Vivi
2013-06-03 11:34 ` Ville Syrjälä
2013-06-03 16:50 ` Rodrigo Vivi
2013-06-03 17:03 ` Ville Syrjälä
2013-06-03 18:41 ` Rodrigo Vivi
2013-06-04 7:06 ` Ville Syrjälä
2013-06-04 8:09 ` Chris Wilson
2013-06-06 14:49 ` Rodrigo Vivi
2013-06-06 15:00 ` Chris Wilson
2013-06-06 15:16 ` Rodrigo Vivi
2013-06-03 17:08 ` Rodrigo Vivi
2013-06-03 17:10 ` Rodrigo Vivi
2013-05-22 10:57 Rodrigo Vivi
2013-05-22 14:21 ` Chris Wilson
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=20130523094845.GB5004@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@gmail.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.