search for: sync_fence_cr

Modify sync_fence_create to accept an array of 'struct fence' objects. This will allow drm drivers to create sync_fence objects and pass sync fd's between user space with minimal modifications, without ever creating sync_timeline or sync_pt objects, and without implementing the sync_timeline_ops interface....

Hi guys, I'd like to start a new thread about explicit fence synchronization. This time with a Nouveau twist. :-) First, let me define what I understand by implicit/explicit sync: Implicit synchronization * Fences are attached to buffers * Kernel manages fences automatically based on buffer read/write access Explicit synchronization * Fences are passed around independently * Kernel takes

...pplies a cooked error code lib/sw_sync: Provide compatiblity stubs for old headers tests/perf: Remove duplicate NSEC_PER_SEC define lib/sw_sync: Bring sync_wait() API into line lib/sw_sync: Indicate that sync_merge() operates and create a sync_fence lib/sw_sync: Rename sync_fence_create() lib/sw_sync: Use timeline/fence instead of generic fd lib/selftest: Query module parameter for error code. lib: Kick all fbcon stubs/intel_bufmgr: Suppress GCC compilation warnings igt/kms_addfb_basic: Try changing tiling on the framebuffer igt/kms_addfb_ba...