Hello,
On 5/21/18, Ezequiel Garcia wrote:
> The in-fence implementation involves having a per-buffer fence callback,
> that triggers on the fence signal. The fence callback is called
> asynchronously
> and needs a valid reference to the associated ideobuf2 buffer.
>
>
Hello,
On 5/21/18, Ezequiel Garcia wrote:
> From: Gustavo Padovan
>
> Receive in-fence from userspace and add support for waiting on them
> before queueing the buffer to the driver. Buffers can't be queued to the
> driver before its fences