Hans Verkuil wrote on Mon [2016-Oct-17 16:17:15 +0200]:
> On 09/28/2016 11:20 PM, Benoit Parrot wrote:
> > From: Nikhil Devshatwar
> >
> > Current VPE driver does not start the job until all the buffers for
> > a transaction are not queued. When running in
Hans Verkuil wrote on Mon [2016-Oct-17 16:17:15 +0200]:
> On 09/28/2016 11:20 PM, Benoit Parrot wrote:
> > From: Nikhil Devshatwar
> >
> > Current VPE driver does not start the job until all the buffers for
> > a transaction are not queued. When running in multiple context, this might
>
> I
On 09/28/2016 11:20 PM, Benoit Parrot wrote:
> From: Nikhil Devshatwar
>
> Current VPE driver does not start the job until all the buffers for
> a transaction are not queued. When running in multiple context, this might
I think this should be: s/not queued/queued/, right?
>
On 09/28/2016 11:20 PM, Benoit Parrot wrote:
> From: Nikhil Devshatwar
>
> Current VPE driver does not start the job until all the buffers for
> a transaction are not queued. When running in multiple context, this might
I think this should be: s/not queued/queued/, right?
> increase the
From: Nikhil Devshatwar
Current VPE driver does not start the job until all the buffers for
a transaction are not queued. When running in multiple context, this might
increase the processing latency.
Alternate solution would be to try to continue the same context as long as
From: Nikhil Devshatwar
Current VPE driver does not start the job until all the buffers for
a transaction are not queued. When running in multiple context, this might
increase the processing latency.
Alternate solution would be to try to continue the same context as long as
buffers for the
6 matches
Mail list logo