Re: [Patch 06/35] media: ti-vpe: vpe: Do not perform job transaction atomically

2016-10-24 Thread Benoit Parrot
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

Re: [Patch 06/35] media: ti-vpe: vpe: Do not perform job transaction atomically

2016-10-24 Thread Benoit Parrot
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

Re: [Patch 06/35] media: ti-vpe: vpe: Do not perform job transaction atomically

2016-10-17 Thread Hans Verkuil
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? >

Re: [Patch 06/35] media: ti-vpe: vpe: Do not perform job transaction atomically

2016-10-17 Thread Hans Verkuil
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