Op 02-07-15 om 04:26 schreef Matt Roper: > Add a simple mechanism to trigger final watermark updates in an > asynchronous manner once the next vblank occurs. No platform types > actually support atomic watermark programming until a future patch, so > there should be no functional change yet; individual platforms will be > converted to use this mechanism one-by-one in future patches. > > Note that we'll probably expand this to cover other post-vblank async > tasks (like unpinning) at some point in the future. > > v2: Much simpler vblank mechanism than was used in the previous series; > no need to allocate new heap structures. > Patch 1-6 are good. But 7 and 8 make my life harder. There is more that needs to be done asynchronously, can you just commit the watermarks synchronously after drm_atomic_helper_wait_for_vblanks for now? ~Maarten _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
