On Mon, Apr 07, 2014 at 11:14:05AM -0300, Paulo Zanoni wrote:
2014-03-07 13:32 GMT-03:00 ville.syrj...@linux.intel.com:
From: Ville Syrjälä ville.syrj...@linux.intel.com
intel_pipe_wm will be used to track the state in different stages
of the watermark update process. For that we need to
On Tue, Apr 29, 2014 at 01:18:50PM +0200, Daniel Vetter wrote:
On Mon, Apr 07, 2014 at 11:14:05AM -0300, Paulo Zanoni wrote:
2014-03-07 13:32 GMT-03:00 ville.syrj...@linux.intel.com:
From: Ville Syrjälä ville.syrj...@linux.intel.com
intel_pipe_wm will be used to track the state in
2014-04-29 8:20 GMT-03:00 Daniel Vetter dan...@ffwll.ch:
On Tue, Apr 29, 2014 at 01:18:50PM +0200, Daniel Vetter wrote:
On Mon, Apr 07, 2014 at 11:14:05AM -0300, Paulo Zanoni wrote:
2014-03-07 13:32 GMT-03:00 ville.syrj...@linux.intel.com:
From: Ville Syrjälä ville.syrj...@linux.intel.com
On Tue, Apr 29, 2014 at 09:34:28AM -0300, Paulo Zanoni wrote:
2014-04-29 8:20 GMT-03:00 Daniel Vetter dan...@ffwll.ch:
On Tue, Apr 29, 2014 at 01:18:50PM +0200, Daniel Vetter wrote:
On Mon, Apr 07, 2014 at 11:14:05AM -0300, Paulo Zanoni wrote:
2014-03-07 13:32 GMT-03:00
2014-03-07 13:32 GMT-03:00 ville.syrj...@linux.intel.com:
From: Ville Syrjälä ville.syrj...@linux.intel.com
intel_pipe_wm will be used to track the state in different stages
of the watermark update process. For that we need to keep a bit
more state in intel_pipe_wm.
We also need to
From: Ville Syrjälä ville.syrj...@linux.intel.com
intel_pipe_wm will be used to track the state in different stages
of the watermark update process. For that we need to keep a bit
more state in intel_pipe_wm.
We also need to separate the multi-pipe intel_wm_config computation
from
