Re: [Intel-gfx] [PATCH] drm/i915/gen9: only add the planes actually affected by ddb changes

2016-09-30 Thread Lyude
Pushed, thanks! On Thu, 2016-09-29 at 16:36 -0300, Paulo Zanoni wrote: > We were previously adding all the planes owned by the CRTC even when > the ddb partitioning didn't change for them. As a consequence, a lot > of functions were being called when we were just moving the cursor > around the

[Intel-gfx] [PATCH] drm/i915/gen9: only add the planes actually affected by ddb changes

2016-09-29 Thread Paulo Zanoni
We were previously adding all the planes owned by the CRTC even when the ddb partitioning didn't change for them. As a consequence, a lot of functions were being called when we were just moving the cursor around the screen, such as skylake_update_primary_plane(). This was causing flickering on

Re: [Intel-gfx] [PATCH] drm/i915/gen9: only add the planes actually affected by ddb changes

2016-09-29 Thread Lyude Paul
On Thu, 2016-09-29 at 15:39 -0300, Paulo Zanoni wrote: > We were previously adding all the planes owned by the CRTC even when > the ddb partitioning didn't change for them. As a consequence, a lot > of functions were being called when we were just moving the cursor > around the screen, such as

[Intel-gfx] [PATCH] drm/i915/gen9: only add the planes actually affected by ddb changes

2016-09-29 Thread Paulo Zanoni
We were previously adding all the planes owned by the CRTC even when the ddb partitioning didn't change for them. As a consequence, a lot of functions were being called when we were just moving the cursor around the screen, such as skylake_update_primary_plane(). This was causing flickering on