Re: [Intel-gfx] [PATCH v2 4/7] drm/omapdrm: Fix omap_atomic_wait_for_completion

2017-08-01 Thread Maarten Lankhorst
Op 25-07-17 om 10:27 schreef Daniel Vetter: > On Wed, Jul 19, 2017 at 04:39:17PM +0200, Maarten Lankhorst wrote: >> Use the new iterator macro and look for crtc_state->active instead of >> enable, only crtc_state->enable implies that vblanks will happen. > s/enable/active/, since enable only means

Re: [Intel-gfx] [PATCH v2 4/7] drm/omapdrm: Fix omap_atomic_wait_for_completion

2017-07-25 Thread Daniel Vetter
On Wed, Jul 19, 2017 at 04:39:17PM +0200, Maarten Lankhorst wrote: > Use the new iterator macro and look for crtc_state->active instead of > enable, only crtc_state->enable implies that vblanks will happen. s/enable/active/, since enable only means logically enabled (aka resources reserved). With