2017-11-17 Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxxxx>:
> Em Fri, 17 Nov 2017 11:12:48 -0200
> Gustavo Padovan <gustavo@xxxxxxxxxxx> escreveu:
>
> > > > /*
> > > > * If streamon has been called, and we haven't yet called
> > > > * start_streaming() since not enough buffers were queued, and
> > > > * we now have reached the minimum number of queued buffers,
> > > > * then we can finally call start_streaming().
> > > > - *
> > > > - * If already streaming, give the buffer to driver for processing.
> > > > - * If not, the buffer will be given to driver on next streamon.
> > > > */
> > > > if (q->streaming && !q->start_streaming_called &&
> > > > - q->queued_count >= q->min_buffers_needed) {
> > > > + __get_num_ready_buffers(q) >= q->min_buffers_needed) {
> > >
> > > I guess the case where fences is not used is not covered here.
> > >
> > > You probably should add a check at __get_num_ready_buffers(q)
> > > as well, making it just return q->queued_count if fences isn't
> > > used.
> >
> > We can't know that beforehand, some buffer ahead may have a fence,
> > but there is already a check for !fence for each buffer. If none of
> > them have fences the return will be equal to q->queued_count.
>
> Hmm... are we willing to support the case where just some
> buffers have fences? Why?
It may be that some fences are already signaled before the QBUF call
happens, so the app may just pass -1 instead.
> In any case, we should add a notice at the documentation telling
> about what happens if not all buffers have fences, and if fences
> are required to be setup before starting streaming, or if it is
> possible to dynamically change the fances behavior while streaming.
We don't have such thing. The fence behavior is tied to each QBUF call,
the stream can be setup without knowing anything about if fences are
going to be used or not. I think we need a good reason to do otherwise.
Yet, I can add something to the docs saying that fences are exclusively
per QBUF call.
Gustavo
