Re: [PATCH v3 1/1] v4l: drop v4l2_buffer.input and V4L2_BUF_FLAG_INPUT

2012-05-28 Thread Hans Verkuil
On Mon May 28 2012 19:25:41 Ezequiel Garcia wrote: > On Mon, May 28, 2012 at 2:10 PM, Hans Verkuil wrote: > >> > >> I may be missing something, but I don't see any relation between > >> video buffer queue and selected input. > >> (Perhaps this is OT and we should discuss this in another thread) >

Re: [PATCH v3 1/1] v4l: drop v4l2_buffer.input and V4L2_BUF_FLAG_INPUT

2012-05-28 Thread Ezequiel Garcia
On Mon, May 28, 2012 at 2:10 PM, Hans Verkuil wrote: >> >> I may be missing something, but I don't see any relation between >> video buffer queue and selected input. >> (Perhaps this is OT and we should discuss this in another thread) > > Well, this particular API was intended to let the hardware

Re: [PATCH v3 1/1] v4l: drop v4l2_buffer.input and V4L2_BUF_FLAG_INPUT

2012-05-28 Thread Hans Verkuil
On Mon May 28 2012 18:29:11 Ezequiel Garcia wrote: > Hi again, > > On Mon, May 28, 2012 at 8:52 AM, Ezequiel Garcia > wrote: > >> I'm just bringing this proposal to your attention as I am wondering how > >> your driver (and > >> the old easycap driver that your driver will replace) handle the e

Re: [PATCH v3 1/1] v4l: drop v4l2_buffer.input and V4L2_BUF_FLAG_INPUT

2012-05-28 Thread Ezequiel Garcia
Hi again, On Mon, May 28, 2012 at 8:52 AM, Ezequiel Garcia wrote: >> I'm just bringing this proposal to your attention as I am wondering how your >> driver (and >> the old easycap driver that your driver will replace) handle the easycap >> device with >> multiple inputs? Is it cycling through a

Re: [PATCH v3 1/1] v4l: drop v4l2_buffer.input and V4L2_BUF_FLAG_INPUT

2012-05-28 Thread Ezequiel Garcia
Hi Hans, On Mon, May 28, 2012 at 7:27 AM, Hans Verkuil wrote: > Hi Ezequiel, > > I'm just bringing this proposal to your attention as I am wondering how your > driver (and > the old easycap driver that your driver will replace) handle the easycap > device with > multiple inputs? Is it cycling t

Re: [PATCH v3 1/1] v4l: drop v4l2_buffer.input and V4L2_BUF_FLAG_INPUT

2012-05-28 Thread Hans Verkuil
Hi Ezequiel, I'm just bringing this proposal to your attention as I am wondering how your driver (and the old easycap driver that your driver will replace) handle the easycap device with multiple inputs? Is it cycling through all inputs? In that case we might need the input field. Regards,

[PATCH v3 1/1] v4l: drop v4l2_buffer.input and V4L2_BUF_FLAG_INPUT

2012-05-02 Thread Sakari Ailus
Remove input field in struct v4l2_buffer and flag V4L2_BUF_FLAG_INPUT which tells the former is valid. The flag is used by no driver currently. Also change the documentation accordingly. Signed-off-by: Sakari Ailus Acked-by: Laurent Pinchart --- Hi, This is the third version of the v4l2_buffer