Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-14 Thread Laurent Pinchart
Hi Guennadi, On Tuesday 14 August 2012 23:14:18 Guennadi Liakhovetski wrote: > On Tue, 14 Aug 2012, Laurent Pinchart wrote: > > On Tuesday 14 August 2012 13:32:43 Hans Verkuil wrote: > > > On Tue August 14 2012 13:15:21 Laurent Pinchart wrote: > > > > On Tuesday 14 August 2012 13:11:49 Hans Verkui

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-14 Thread Guennadi Liakhovetski
On Tue, 14 Aug 2012, Laurent Pinchart wrote: > On Tuesday 14 August 2012 13:32:43 Hans Verkuil wrote: > > On Tue August 14 2012 13:15:21 Laurent Pinchart wrote: > > > On Tuesday 14 August 2012 13:11:49 Hans Verkuil wrote: > > > > On Tue August 14 2012 13:06:46 Laurent Pinchart wrote: > > > > > On

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-14 Thread Chinmay V S
On Tue, Aug 14, 2012 at 6:13 PM, Hans de Goede wrote: > Hi, > > > On 08/14/2012 12:54 PM, Hans Verkuil wrote: >> >> On Tue August 14 2012 01:54:16 Laurent Pinchart wrote: >>> >>> Hi Hans, >>> >>> On Monday 13 August 2012 14:27:56 Hans Verkuil wrote: Hi all! As part of the 2012

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-14 Thread Hans de Goede
Hi, On 08/14/2012 12:54 PM, Hans Verkuil wrote: On Tue August 14 2012 01:54:16 Laurent Pinchart wrote: Hi Hans, On Monday 13 August 2012 14:27:56 Hans Verkuil wrote: Hi all! As part of the 2012 Kernel Summit V4L2 workshop I will be discussing a bunch of V4L2 ambiguities/improvements. I've m

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-14 Thread Laurent Pinchart
On Tuesday 14 August 2012 13:32:43 Hans Verkuil wrote: > On Tue August 14 2012 13:15:21 Laurent Pinchart wrote: > > On Tuesday 14 August 2012 13:11:49 Hans Verkuil wrote: > > > On Tue August 14 2012 13:06:46 Laurent Pinchart wrote: > > > > On Tuesday 14 August 2012 12:54:34 Hans Verkuil wrote: > >

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-14 Thread Hans Verkuil
On Tue August 14 2012 13:15:21 Laurent Pinchart wrote: > Hi Hans, > > On Tuesday 14 August 2012 13:11:49 Hans Verkuil wrote: > > On Tue August 14 2012 13:06:46 Laurent Pinchart wrote: > > > On Tuesday 14 August 2012 12:54:34 Hans Verkuil wrote: > > > > On Tue August 14 2012 01:54:16 Laurent Pincha

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-14 Thread Laurent Pinchart
Hi Hans, On Tuesday 14 August 2012 13:11:49 Hans Verkuil wrote: > On Tue August 14 2012 13:06:46 Laurent Pinchart wrote: > > On Tuesday 14 August 2012 12:54:34 Hans Verkuil wrote: > > > On Tue August 14 2012 01:54:16 Laurent Pinchart wrote: > > > > On Monday 13 August 2012 14:27:56 Hans Verkuil wr

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-14 Thread Hans Verkuil
On Tue August 14 2012 13:06:46 Laurent Pinchart wrote: > Hi Hans, > > On Tuesday 14 August 2012 12:54:34 Hans Verkuil wrote: > > On Tue August 14 2012 01:54:16 Laurent Pinchart wrote: > > > On Monday 13 August 2012 14:27:56 Hans Verkuil wrote: > > > > Hi all! > > > > > > > > As part of the 2012 K

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-14 Thread Laurent Pinchart
Hi Hans, On Tuesday 14 August 2012 12:54:34 Hans Verkuil wrote: > On Tue August 14 2012 01:54:16 Laurent Pinchart wrote: > > On Monday 13 August 2012 14:27:56 Hans Verkuil wrote: > > > Hi all! > > > > > > As part of the 2012 Kernel Summit V4L2 workshop I will be discussing a > > > bunch of V4L2 a

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-14 Thread Hans Verkuil
On Tue August 14 2012 01:54:16 Laurent Pinchart wrote: > Hi Hans, > > On Monday 13 August 2012 14:27:56 Hans Verkuil wrote: > > Hi all! > > > > As part of the 2012 Kernel Summit V4L2 workshop I will be discussing a bunch > > of V4L2 ambiguities/improvements. > > > > I've made a list of all the V

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-14 Thread Hans de Goede
Hi, On 08/14/2012 02:00 AM, Laurent Pinchart wrote: Hi Hans, On Monday 13 August 2012 15:13:34 Hans de Goede wrote: [snip] 4) What should a driver return in TRY_FMT/S_FMT if the requested format is not supported (possible behaviours include returning the currently selected format o

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-14 Thread Hans de Goede
Hi, On 08/13/2012 09:15 PM, Sylwester Nawrocki wrote: And if a driver also supports single-plane formats in addition to >1 plane formats, should V4L2_CAP_VIDEO_CAPTURE be compulsary? Yes, so that non multi-plane aware apps keep working. There is the multi-planar API and there are multi-pla

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-13 Thread Laurent Pinchart
Hi Hans, On Monday 13 August 2012 15:13:34 Hans de Goede wrote: [snip] > > 4) What should a driver return in TRY_FMT/S_FMT if the requested format is > > not supported (possible behaviours include returning the currently > > selected format or a default format). > > > > The spec

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-13 Thread Laurent Pinchart
Hi Hans, On Monday 13 August 2012 14:27:56 Hans Verkuil wrote: > Hi all! > > As part of the 2012 Kernel Summit V4L2 workshop I will be discussing a bunch > of V4L2 ambiguities/improvements. > > I've made a list of all the V4L2 issues and put them in two categories: > issues that I think are easy

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-13 Thread Sylwester Nawrocki
Hi! On 08/13/2012 03:13 PM, Hans de Goede wrote: >> 2) If a driver supports only formats with more than one plane, should >> V4L2_CAP_VIDEO_CAPTURE still be defined? > > No Agreed. >> And if a driver also supports >> single-plane formats in addition to >1 plane formats, should >> V4L2_CAP_VIDEO

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-13 Thread Rémi Denis-Courmont
Le lundi 13 août 2012 15:27:56 Hans Verkuil, vous avez écrit : > 1) What is the right/best way to set the timestamp? The spec says > gettimeofday, but is it my understanding that ktime_get_ts is much more > efficient. > >Some drivers are already using ktime_get_ts. > >Options: > >a)

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-13 Thread Ilyes Gouta
Hi, I've got one limitation for v4l2-mem2mem devices: a v4l2-mem2mem device driver which can't support *both* V4L2_BUF_TYPE_VIDEO_CAPTURE and V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE capture buffers. AFAIK/U, this limitation is unjustified. So, with v4l2-mem2mem : 1. It's not possible to alternativel

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-13 Thread Hans de Goede
Hi, On 08/13/2012 04:52 PM, Hans Verkuil wrote: On Mon August 13 2012 15:13:34 Hans de Goede wrote: Hi, 5) How to handle tuner ownership if both a video and radio node share the same tuner? Obvious rules: - Calling S_FREQ, S_TUNER, S_MODULATOR or S_HW_FREQ_SEEK will change

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-13 Thread Hans Verkuil
On Mon August 13 2012 15:13:34 Hans de Goede wrote: > Hi, > > > > > 5) How to handle tuner ownership if both a video and radio node share the > > same > > tuner? > > > > Obvious rules: > > > > - Calling S_FREQ, S_TUNER, S_MODULATOR or S_HW_FREQ_SEEK will change > > owner > >

Re: [Workshop-2011] RFC: V4L2 API ambiguities

2012-08-13 Thread Hans de Goede
Hi, Easy: 1) Split off the control part from videodev2.h. Controls are almost 30% of videodev2.h. I think maintaining controls would be easier if they are moved to e.g. linux/v4l2-controls.h which is included by videodev2.h. Ack. 2) Currently there are three types of controls: st