Re: [Intel-gfx] [RFC 7/8] drm/i915: Allow final wm programming to be scheduled after next vblank (v2)

2015-07-20 Thread Maarten Lankhorst
Op 02-07-15 om 04:26 schreef Matt Roper: Add a simple mechanism to trigger final watermark updates in an asynchronous manner once the next vblank occurs. No platform types actually support atomic watermark programming until a future patch, so there should be no functional change yet;

Re: [Intel-gfx] [RFC 7/8] drm/i915: Allow final wm programming to be scheduled after next vblank (v2)

2015-07-06 Thread Daniel Vetter
On Wed, Jul 01, 2015 at 07:26:00PM -0700, Matt Roper wrote: Add a simple mechanism to trigger final watermark updates in an asynchronous manner once the next vblank occurs. No platform types actually support atomic watermark programming until a future patch, so there should be no functional

Re: [Intel-gfx] [RFC 7/8] drm/i915: Allow final wm programming to be scheduled after next vblank (v2)

2015-07-06 Thread Ville Syrjälä
On Mon, Jul 06, 2015 at 11:07:52AM +0200, Daniel Vetter wrote: On Wed, Jul 01, 2015 at 07:26:00PM -0700, Matt Roper wrote: Add a simple mechanism to trigger final watermark updates in an asynchronous manner once the next vblank occurs. No platform types actually support atomic watermark

[Intel-gfx] [RFC 7/8] drm/i915: Allow final wm programming to be scheduled after next vblank (v2)

2015-07-01 Thread Matt Roper
Add a simple mechanism to trigger final watermark updates in an asynchronous manner once the next vblank occurs. No platform types actually support atomic watermark programming until a future patch, so there should be no functional change yet; individual platforms will be converted to use this