On Wed, Jun 04, 2014 at 06:10:44PM +0200, Daniel Vetter wrote:
On Wed, Jun 04, 2014 at 11:01:01AM -0300, Paulo Zanoni wrote:
This function is only called at init/resume. It populates the software
state with something that matches the current hardware state. I guess
a comment explaning
2014-06-03 16:32 GMT-03:00 Ville Syrjälä ville.syrj...@linux.intel.com:
On Tue, Jun 03, 2014 at 03:50:12PM -0300, Paulo Zanoni wrote:
2014-05-22 11:48 GMT-03:00 ville.syrj...@linux.intel.com:
From: Ville Syrjälä ville.syrj...@linux.intel.com
Add a mechanism by which you can queue up
On Wed, Jun 04, 2014 at 11:01:01AM -0300, Paulo Zanoni wrote:
This function is only called at init/resume. It populates the software
state with something that matches the current hardware state. I guess
a comment explaning the purpose of the function is the best we can do
here, or do you
2014-05-22 11:48 GMT-03:00 ville.syrj...@linux.intel.com:
From: Ville Syrjälä ville.syrj...@linux.intel.com
Add a mechanism by which you can queue up watermark update to happen
after the vblank counter has reached a certain value. The vblank
interrupt handler will schedule a work which will
On Tue, Jun 03, 2014 at 03:50:12PM -0300, Paulo Zanoni wrote:
2014-05-22 11:48 GMT-03:00 ville.syrj...@linux.intel.com:
From: Ville Syrjälä ville.syrj...@linux.intel.com
Add a mechanism by which you can queue up watermark update to happen
after the vblank counter has reached a certain
From: Ville Syrjälä ville.syrj...@linux.intel.com
Add a mechanism by which you can queue up watermark update to happen
after the vblank counter has reached a certain value. The vblank
interrupt handler will schedule a work which will do the actual
watermark programming in process context.
v2:
