From: Damien Lespiau <damien.lespiau@intel.com>
To: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com>
Cc: intel-gfx@lists.freedesktop.org, ville.syrjala@intel.com,
shuang.he@linux.intel.com, paulo.zanoni@intel.com
Subject: Re: [PATCH 3/3] drm/i915: Use vblank evade mechanism in mmio_flip
Date: Tue, 28 Oct 2014 14:18:01 +0000 [thread overview]
Message-ID: <20141028141801.GA29136@strange.ger.corp.intel.com> (raw)
In-Reply-To: <1414501814-1465-3-git-send-email-ander.conselvan.de.oliveira@intel.com>
On Tue, Oct 28, 2014 at 03:10:14PM +0200, Ander Conselvan de Oliveira wrote:
> Currently we program just DPSCNTR and DSPSTRIDE directly from the ring
> interrupt handler, which is fine since the hardware guarantees that
> those are update atomically. When we have atomic page flips we'll want
> to be able to update also the offset registers, and then we need to use
> the vblank evade mechanism to guarantee atomicity. Since that mechanism
> introduces a wait, we need to do the actual register write from a work
> when it is triggered by the ring interrupt.
>
> v2: Explain the need for mmio_flip.work in the commit message (Paulo)
> Initialize the mmio_flip work in intel_crtc_init() (Paulo)
> Prevent new flips the previous flip work finishes (Paulo)
> Don't acquire modeset locks for mmio flip work
So that means you can replace the content of intel_do_mmio() by a call
to dev_priv->display.update_primary_plane() on top of this patch? That'd
do the right thing on SKL, which would make me happy.
--
Damien
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-10-28 14:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 13:10 [PATCH 1/3] drm/i915: Add kerneldoc for intel_pipe_update_{start, end} Ander Conselvan de Oliveira
2014-10-28 13:10 ` [PATCH 2/3] drm/i915: Remove modeset lock check from intel_pipe_update_start() Ander Conselvan de Oliveira
2014-10-28 13:10 ` [PATCH 3/3] drm/i915: Use vblank evade mechanism in mmio_flip Ander Conselvan de Oliveira
2014-10-28 14:18 ` Damien Lespiau [this message]
2014-11-03 18:37 ` Paulo Zanoni
2014-11-03 18:53 ` Daniel Vetter
2014-11-03 19:13 ` Paulo Zanoni
2014-11-03 19:24 ` Daniel Vetter
2014-11-04 8:48 ` Ander Conselvan de Oliveira
2014-11-04 11:04 ` Daniel Vetter
2014-11-04 11:10 ` Chris Wilson
2014-11-05 11:03 ` [PATCH] drm/i915: Make mmio flip wait for seqno in the work function Ander Conselvan de Oliveira
2014-11-05 11:23 ` Chris Wilson
2014-11-05 12:23 ` Ander Conselvan de Oliveira
2014-11-05 12:29 ` Chris Wilson
2014-11-06 7:26 ` [PATCH 1/2] drm/i915: Make __wait_seqno non-static and rename to __i915_wait_seqno Ander Conselvan de Oliveira
2014-11-06 7:26 ` [PATCH 2/2] drm/i915: Make mmio flip wait for seqno in the work function Ander Conselvan de Oliveira
2014-11-06 7:47 ` Chris Wilson
2014-11-06 9:03 ` [PATCH] " Ander Conselvan de Oliveira
2014-11-06 9:25 ` Chris Wilson
2014-11-06 13:53 ` Daniel Vetter
2014-11-06 14:33 ` Chris Wilson
2014-11-03 12:33 ` [PATCH 1/3] drm/i915: Add kerneldoc for intel_pipe_update_{start, end} Daniel Vetter
2014-11-03 12:41 ` Ander Conselvan de Oliveira
2014-11-03 17:26 ` Paulo Zanoni
2014-11-03 18:19 ` Daniel Vetter
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=20141028141801.GA29136@strange.ger.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.zanoni@intel.com \
--cc=shuang.he@linux.intel.com \
--cc=ville.syrjala@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