Re: [RFCv11 PATCH 27/29] vim2m: support requests

2018-04-23 Thread Hans Verkuil
On 04/17/2018 01:42 PM, Paul Kocialkowski wrote: > Hi, > > On Mon, 2018-04-09 at 16:20 +0200, Hans Verkuil wrote: >> From: Hans Verkuil >> >> Add support for requests to vim2m. > > Please find a nit below. > >> Signed-off-by: Hans Verkuil >> ---

Re: [RFCv11 PATCH 27/29] vim2m: support requests

2018-04-23 Thread Hans Verkuil
On 04/17/2018 06:37 AM, Alexandre Courbot wrote: > On Mon, Apr 9, 2018 at 11:20 PM Hans Verkuil wrote: > >> From: Hans Verkuil > >> Add support for requests to vim2m. > >> Signed-off-by: Hans Verkuil >> --- >>

Re: [RFCv11 PATCH 27/29] vim2m: support requests

2018-04-23 Thread Hans Verkuil
On 04/12/2018 11:15 AM, Tomasz Figa wrote: > Hi Hans, > > On Mon, Apr 9, 2018 at 11:20 PM Hans Verkuil wrote: > >> From: Hans Verkuil > >> Add support for requests to vim2m. > >> Signed-off-by: Hans Verkuil >> --- >>

Re: [RFCv11 PATCH 27/29] vim2m: support requests

2018-04-17 Thread Paul Kocialkowski
Hi, On Mon, 2018-04-09 at 16:20 +0200, Hans Verkuil wrote: > From: Hans Verkuil > > Add support for requests to vim2m. Please find a nit below. > Signed-off-by: Hans Verkuil > --- > drivers/media/platform/vim2m.c | 25 +

Re: [RFCv11 PATCH 27/29] vim2m: support requests

2018-04-16 Thread Alexandre Courbot
On Mon, Apr 9, 2018 at 11:20 PM Hans Verkuil wrote: > From: Hans Verkuil > Add support for requests to vim2m. > Signed-off-by: Hans Verkuil > --- > drivers/media/platform/vim2m.c | 25 + > 1 file

Re: [RFCv11 PATCH 27/29] vim2m: support requests

2018-04-12 Thread Tomasz Figa
Hi Hans, On Mon, Apr 9, 2018 at 11:20 PM Hans Verkuil wrote: > From: Hans Verkuil > Add support for requests to vim2m. > Signed-off-by: Hans Verkuil > --- > drivers/media/platform/vim2m.c | 25 + >

Re: [RFCv11 PATCH 27/29] vim2m: support requests

2018-04-11 Thread Paul Kocialkowski
Hi, On Mon, 2018-04-09 at 16:20 +0200, Hans Verkuil wrote: > From: Hans Verkuil > > Add support for requests to vim2m. Depending on where STREAMON happens in the sequence, there is a possibility that v4l2_m2m_try_schedule is never called and thus that device_run never