drm/atomic-helpers: Properly avoid full modeset dance

2015-03-27 Thread Dan Carpenter
Hello Daniel Vetter, This is a semi-automatic email about new static checker warnings. The patch 76b58b03806b: "drm/atomic-helpers: Properly avoid full modeset dance" from Mar 26, 2015, leads to the following Smatch complaint: drivers/gpu/drm/drm_atomic_helper.c:615 disab

drm/atomic-helpers: Properly avoid full modeset dance

2015-03-27 Thread Daniel Vetter
On Fri, Mar 27, 2015 at 05:33:00PM +0300, Dan Carpenter wrote: > Hello Daniel Vetter, > > This is a semi-automatic email about new static checker warnings. > > The patch 76b58b03806b: "drm/atomic-helpers: Properly avoid full > modeset dance" from Mar 26, 2015, l

[PATCH] drm/atomic-helpers: Properly avoid full modeset dance

2015-03-27 Thread Daniel Vetter
Legacy setCrtc has a nice fastpath for just updating the frontbuffer when the output routing doesn't change. Which I of course tried to keep working, except that I fumbled the job: The helpers correctly compute ->mode_changed, CRTC updates get correctly skipped but connector functions are called un

[Intel-gfx] [PATCH] drm/atomic-helpers: Properly avoid full modeset dance

2015-03-27 Thread Gustavo Padovan
2015-03-27 Daniel Vetter : > Legacy setCrtc has a nice fastpath for just updating the frontbuffer > when the output routing doesn't change. Which I of course tried to > keep working, except that I fumbled the job: The helpers correctly > compute ->mode_changed, CRTC updates get correctly skipped b

[PATCH] drm/atomic-helpers: Properly avoid full modeset dance

2015-03-26 Thread Daniel Vetter
Legacy setCrtc has a nice fastpath for just updating the frontbuffer when the output routing doesn't change. Which I of course tried to keep working, except that I fumbled the job: The helpers correctly compute ->mode_changed, CRTC updates get correctly skipped but connector functions are called un