On Wed, Jun 04, 2014 at 11:30:47AM +0530, Arun Murthy wrote:
On Mon, May 26, 2014 at 7:26 PM, Daniel Vetter dan...@ffwll.ch wrote:
On Thu, May 22, 2014 at 05:48:06PM +0300, ville.syrj...@linux.intel.com
wrote:
From: Ville Syrjälä ville.syrj...@linux.intel.com
Because of the upcoming
On Mon, May 26, 2014 at 7:26 PM, Daniel Vetter dan...@ffwll.ch wrote:
On Thu, May 22, 2014 at 05:48:06PM +0300, ville.syrj...@linux.intel.com wrote:
From: Ville Syrjälä ville.syrj...@linux.intel.com
Because of the upcoming vblank interrupt driven watermark update
mechanism we will have use
On Thu, May 22, 2014 at 05:48:06PM +0300, ville.syrj...@linux.intel.com wrote:
From: Ville Syrjälä ville.syrj...@linux.intel.com
Because of the upcoming vblank interrupt driven watermark update
mechanism we will have use for vblank interrupts during plane
enabling/disabling. So don't call
From: Ville Syrjälä ville.syrj...@linux.intel.com
Because of the upcoming vblank interrupt driven watermark update
mechanism we will have use for vblank interrupts during plane
enabling/disabling. So don't call drm_vblank_off() until planes
are off, and call drm_vblank_on() just before we start
