1. 11 8月, 2016 1 次提交
    • G
      dma-buf/sync_file: refactor fence storage in struct sync_file · a02b9dc9
      Gustavo Padovan 提交于
      Create sync_file->fence to abstract the type of fence we are using for
      each sync_file. If only one fence is present we use a normal struct fence
      but if there is more fences to be added to the sync_file a fence_array
      is created.
      
      This change cleans up sync_file a bit. We don't need to have sync_file_cb
      array anymore. Instead, as we always have  one fence, only one fence
      callback is registered per sync_file.
      
      v2: Comments from Chris Wilson and Christian König
      	- Not using fence_ops anymore
      	- fence_is_array() was created to differentiate fence from fence_array
      	- fence_array_teardown() is now exported and used under fence_is_array()
      	- struct sync_file lost num_fences member
      
      v3: Comments from Chris Wilson and Christian König
      	- struct sync_file lost status member in favor of fence_is_signaled()
      	- drop use of fence_array_teardown()
      	- use sizeof(*fence) to allocate only an array on fence pointers
      
      v4: Comments from Chris Wilson
      	- use sizeof(*fence) to reallocate array
      	- fix typo in comments
      	- protect num_fences sum against overflows
      	- use array->base instead of casting the to struct fence
      
      v5: fixes checkpatch warnings
      
      v6: fix case where all fences are signaled.
      Signed-off-by: NGustavo Padovan <gustavo.padovan@collabora.co.uk>
      Reviewed-by: NChris Wilson <chris@chris-wilson.co.uk>
      Acked-by: NChristian König <christian.koenig@amd.com>
      Acked-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Signed-off-by: NSumit Semwal <sumit.semwal@linaro.org>
      a02b9dc9
  2. 30 4月, 2016 3 次提交