public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	linux-media@vger.kernel.org,
	Javier Martinez Canillas <javier@osg.samsung.com>,
	Shuah Khan <shuahkh@osg.samsung.com>,
	Gustavo Padovan <gustavo.padovan@collabora.com>
Subject: Re: [PATCH 03/12] [media] vb2: add in-fence support to QBUF
Date: Thu, 6 Jul 2017 22:12:34 -0300	[thread overview]
Message-ID: <20170707011234.GC10284@jade> (raw)
In-Reply-To: <3e403e98-c9f0-1020-87c3-36aff44d5354@xs4all.nl>

2017-07-06 Hans Verkuil <hverkuil@xs4all.nl>:

> On 07/03/17 20:16, Gustavo Padovan wrote:
> >>> @@ -1436,6 +1481,11 @@ int vb2_core_qbuf(struct vb2_queue *q, unsigned int index, void *pb)
> >>>  	if (pb)
> >>>  		call_void_bufop(q, fill_user_buffer, vb, pb);
> >>>  
> >>> +	vb->in_fence = fence;
> >>> +	if (fence && !dma_fence_add_callback(fence, &vb->fence_cb,
> >>> +					     vb2_qbuf_fence_cb))
> >>> +		return 0;
> >>
> >> Maybe we should provide some error or debug log here or a WARN_ON(), if 
> >> dma_fence_add_callback() fails instead of silently ignore any errors.
> > 
> > This is not an error. If the if succeeds it mean we have installed a
> > callback for the fence. If not, it means the fence signaled already and
> > we don't can call __vb2_core_qbuf right away.
> 
> I had the same question as Mauro. After looking at the dma_fence_add_callback
> code I see what you mean, but a comment would certainly be helpful.

Sure, I'll add a comment explaining it.

> 
> Also, should you set vb->in_fence to NULL if the fence signaled already?
> I'm not sure if you need to call 'dma_fence_put(vb->in_fence);' as well.
> You would know that better than I do.

You got it right. I should be doing that.

Gustavo

  reply	other threads:[~2017-07-07  1:12 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16  7:39 [PATCH 00/12] V4L2 explicit synchronization support Gustavo Padovan
2017-06-16  7:39 ` [PATCH 01/12] [media] vb2: add explicit fence user API Gustavo Padovan
2017-06-18 14:09   ` kbuild test robot
2017-06-18 14:58   ` kbuild test robot
2017-06-26 15:39     ` Gustavo Padovan
2017-07-04  5:57       ` Tomasz Figa
2017-07-04  6:27         ` Alexandre Courbot
2017-06-30 11:12   ` Mauro Carvalho Chehab
2017-06-16  7:39 ` [PATCH 02/12] [media] vb2: split out queueing from vb_core_qbuf() Gustavo Padovan
2017-06-30 11:15   ` Mauro Carvalho Chehab
2017-07-06  7:46   ` Hans Verkuil
2017-07-07  1:04     ` Gustavo Padovan
2017-06-16  7:39 ` [PATCH 03/12] [media] vb2: add in-fence support to QBUF Gustavo Padovan
2017-06-18 15:36   ` kbuild test robot
2017-06-30 11:53   ` Mauro Carvalho Chehab
2017-07-03 18:16     ` Gustavo Padovan
2017-07-06  9:43       ` Hans Verkuil
2017-07-07  1:12         ` Gustavo Padovan [this message]
2017-07-06  8:29   ` Hans Verkuil
2017-07-07  1:53     ` Gustavo Padovan
2017-07-07  7:15       ` Hans Verkuil
2017-07-10 19:27         ` Gustavo Padovan
2017-07-06  9:18   ` Hans Verkuil
2017-07-07  2:00     ` Gustavo Padovan
2017-07-07  7:06       ` Hans Verkuil
2017-07-10 19:02         ` Gustavo Padovan
2017-07-10 20:26           ` Gustavo Padovan
2017-07-11  5:57             ` Hans Verkuil
2017-07-11 12:56               ` Gustavo Padovan
2017-06-16  7:39 ` [PATCH 04/12] [media] uvc: enable subscriptions to other events Gustavo Padovan
2017-07-07 14:38   ` Shuah Khan
2017-07-10 19:38     ` Gustavo Padovan
2017-07-26  0:26       ` Gustavo Padovan
2017-06-16  7:39 ` [PATCH 05/12] [media] vivid: assign the specific device to the vb2_queue->dev Gustavo Padovan
2017-07-06  8:36   ` Hans Verkuil
2017-07-07 17:15   ` Shuah Khan
2017-07-10 19:42     ` Gustavo Padovan
2017-07-26  0:17     ` Gustavo Padovan
2017-06-16  7:39 ` [PATCH 06/12] [media] v4l: add V4L2_EVENT_BUF_QUEUED event Gustavo Padovan
2017-06-30 12:00   ` Mauro Carvalho Chehab
2017-06-16  7:39 ` [PATCH 07/12] [media] v4l: add support to BUF_QUEUED event Gustavo Padovan
2017-06-30 12:04   ` Mauro Carvalho Chehab
2017-07-03 18:36     ` Gustavo Padovan
2017-07-06  9:34     ` Hans Verkuil
2017-07-10 19:45       ` Gustavo Padovan
2017-07-06  8:47   ` Hans Verkuil
2017-06-16  7:39 ` [PATCH 08/12] [media] vb2: add 'ordered' property to queues Gustavo Padovan
2017-06-16 16:56   ` Nicolas Dufresne
2017-06-26 15:22     ` Gustavo Padovan
2017-07-06  9:08   ` Hans Verkuil
2017-06-16  7:39 ` [PATCH 09/12] [media] vivid: mark vivid queues as ordered Gustavo Padovan
2017-07-06  8:37   ` Hans Verkuil
2017-07-07 17:31   ` Shuah Khan
2017-07-10 19:47     ` Gustavo Padovan
2017-06-16  7:39 ` [PATCH 10/12] [media] vb2: add videobuf2 dma-buf fence helpers Gustavo Padovan
2017-06-16  7:39 ` [PATCH 11/12] [media] vb2: add infrastructure to support out-fences Gustavo Padovan
2017-06-16  7:39 ` [PATCH 12/12] [media] vb2: add out-fence support to QBUF Gustavo Padovan
2017-07-06  9:27   ` Hans Verkuil
2017-07-06  9:29   ` Hans Verkuil
2017-07-10 20:19     ` Gustavo Padovan
2017-06-30 12:18 ` [PATCH 00/12] V4L2 explicit synchronization support Mauro Carvalho Chehab
2017-07-03 18:40   ` Gustavo Padovan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170707011234.GC10284@jade \
    --to=gustavo@padovan.org \
    --cc=gustavo.padovan@collabora.com \
    --cc=hverkuil@xs4all.nl \
    --cc=javier@osg.samsung.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=shuahkh@osg.samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox