Re: [PATCH weston v5 30/42] compositor-drm: Introduce drm_output_state structure

2016-12-08 Thread Fabien DESSENNE
On 08/12/16 13:58, Daniel Stone wrote: > Hi Fabien, > > On 21 November 2016 at 14:58, Fabien DESSENNE wrote: >> On 11/16/2016 03:25 PM, Daniel Stone wrote: >>> +/** >>> + * Mark a drm_output_state (the output's last state) as complete. This >>> handles >>> + * any post-completion actions such a

Re: [PATCH weston v5 30/42] compositor-drm: Introduce drm_output_state structure

2016-12-08 Thread Daniel Stone
Hi Fabien, On 21 November 2016 at 14:58, Fabien DESSENNE wrote: > On 11/16/2016 03:25 PM, Daniel Stone wrote: >> +/** >> + * Mark a drm_output_state (the output's last state) as complete. This >> handles >> + * any post-completion actions such as updating the repaint timer, >> disabling the >>

Re: [PATCH weston v5 30/42] compositor-drm: Introduce drm_output_state structure

2016-11-21 Thread Fabien DESSENNE
Hi Daniel On 11/16/2016 03:25 PM, Daniel Stone wrote: > Currently this doesn't actually really do anything, but will be used in > the future to track the state for both modeset and repaint requests. > Completion of the request gives us a single request-completion path for > both pageflip and vbl

[PATCH weston v5 30/42] compositor-drm: Introduce drm_output_state structure

2016-11-16 Thread Daniel Stone
Currently this doesn't actually really do anything, but will be used in the future to track the state for both modeset and repaint requests. Completion of the request gives us a single request-completion path for both pageflip and vblank events. Signed-off-by: Daniel Stone Differential Revision: