Re: [PATCH v14 11/41] compositor-drm: Move repaint state application to flush

2018-01-17 Thread Daniel Stone
Hi, On 17 January 2018 at 13:58, Pekka Paalanen wrote: > this is still a tricky one, sorry. > > I looked at the details here hard and long, and then came to a > revelation: is it at all possible to ever call drm_set_dpms() between > repaint_begin and repaint_flush/cancel? > > I don't think it is

Re: [PATCH v14 11/41] compositor-drm: Move repaint state application to flush

2018-01-17 Thread Pekka Paalanen
On Wed, 20 Dec 2017 12:26:28 + Daniel Stone wrote: > Split repaint into two stages, as implied by the grouped-repaint > interface: drm_output_repaint generates the repaint state only, and > drm_repaint_flush applies it. > > This also moves DPMS into output state. Previously, the usual way to

[PATCH v14 11/41] compositor-drm: Move repaint state application to flush

2017-12-20 Thread Daniel Stone
Split repaint into two stages, as implied by the grouped-repaint interface: drm_output_repaint generates the repaint state only, and drm_repaint_flush applies it. This also moves DPMS into output state. Previously, the usual way to DPMS off was that repaint would be called and apply its state, fol