[PATCH] drm: Handle atomic state properly in kms getfoo ioctl

2014-11-26 Thread Daniel Vetter
On Wed, Nov 26, 2014 at 10:52:24AM -0500, Sean Paul wrote: > On Tue, Nov 25, 2014 at 5:50 PM, Daniel Vetter > wrote: > > So the problem with async commit (especially async modeset commit) is > > that the legacy pointers only get updated after the point of no > > return, in the async part of the m

[PATCH] drm: Handle atomic state properly in kms getfoo ioctl

2014-11-26 Thread Sean Paul
On Tue, Nov 25, 2014 at 5:50 PM, Daniel Vetter wrote: > So the problem with async commit (especially async modeset commit) is > that the legacy pointers only get updated after the point of no > return, in the async part of the modeset sequence. At least as > implemented by the current helper func

[PATCH] drm: Handle atomic state properly in kms getfoo ioctl

2014-11-25 Thread Daniel Vetter
So the problem with async commit (especially async modeset commit) is that the legacy pointers only get updated after the point of no return, in the async part of the modeset sequence. At least as implemented by the current helper functions. This is done in the set_routing_links function in drm_ato