linux-toradex.git/include/linux/videodev2.h, branch v3.0.29

V4L/DVB: v4l2-ioctl: integer overflow in video_usercopy()

2012-01-26T01:24:46+00:00

commit 6c06108be53ca5e94d8b0e93883d534dd9079646 upstream.

If ctrls->count is too high the multiplication could overflow and
array_size would be lower than expected.  Mauro and Hans Verkuil
suggested that we cap it at 1024.  That comes from the maximum
number of controls with lots of room for expantion.

$ grep V4L2_CID include/linux/videodev2.h | wc -l
211

Signed-off-by: Dan Carpenter 
Signed-off-by: Mauro Carvalho Chehab 
Signed-off-by: Greg Kroah-Hartman

[media] v4l: Add M420 format definition

2011-05-20T15:17:35+00:00

M420 is a hybrid YUV 4:2:0 packet/planar format. Two Y lines are
followed by an interleaved U/V line.

Signed-off-by: Hans de Goede 
[laurent.pinchart@ideasonboard.com: split into v4l/uvcvideo patches]
[laurent.pinchart@ideasonboard.com: add documentation]
Signed-off-by: Laurent Pinchart 
Signed-off-by: Mauro Carvalho Chehab

[media] Add Y10B, a 10 bpp bit-packed greyscale format

2011-05-20T12:27:26+00:00

Add a 10 bits per pixel greyscale format in a bit-packed array representation,
naming it Y10B. Such pixel format is supplied for instance by the Kinect
sensor device.

Signed-off-by: Antonio Ospite 
Signed-off-by: Jean-François Moine 
Signed-off-by: Mauro Carvalho Chehab

[media] v4l: add V4L2_PIX_FMT_Y12 format

2011-04-19T14:20:56+00:00

Y12 is a grey-scale format with a depth of 12 bits per pixel stored in
16-bit words.

Signed-off-by: Michael Jones 
Acked-by: Laurent Pinchart 
Signed-off-by: Mauro Carvalho Chehab

[media] gspca - nw80x: New subdriver for Divio based webcams

2011-03-22T07:54:51+00:00

[mchehab@redhat.com: Fix a few CodingStyle issues]
Tested-by: Kjell Claesson 
Tested-by: Hans de Goede 
Signed-off-by: Jean-François Moine 
Signed-off-by: Mauro Carvalho Chehab

[media] v4l: Add 12 bits bayer pixel formats

2011-03-22T07:53:38+00:00

Add FCCs for the following pixel formats:

- V4L2_PIX_FMT_SBGGR12
- V4L2_PIX_FMT_SGBRG12
- V4L2_PIX_FMT_SGRBG12
- V4L2_PIX_FMT_SRGGB12

Signed-off-by: Laurent Pinchart 
Acked-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

[media] v4l: removal of old, obsolete ioctls

2011-03-21T23:32:12+00:00

Some ioctl's were defined wrong on 2.6.2 and 2.6.6, using the wrong
type of R/W arguments. They were fixed, but the old ioctl names are
still there, maintained to avoid breaking binary compatibility:

There's no sense on preserving those forever, as it is very doubtful
that someone would try to use a such old binary with a modern kernel.
Removing them will allow us to remove some magic done at the V4L ioctl
handler.

Note that any application compiled with a videodev2.h from 2.6.7 or later
will be using the correct ioctls.

Signed-off-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

[media] v4l: Add multiplanar format fourccs for s5p-fimc driver

2011-03-21T23:31:35+00:00

Add definitions for format with color planes non-contiguous
in physical memory. These formats apply only if the V4L2 multiplane
extension is used.

V4L2_PIX_FMT_NV12M   - 2-plane Y/CbCr
V4L2_PIX_FMT_NV12MT  - 2-plane Y/CbCr tiled (64x32 pixel macroblocks)
V4L2_PIX_FMT_YUV420M - 3-plane Y/Cb/Cr

Signed-off-by: Sylwester Nawrocki 
Signed-off-by: Kyungmin Park 
Signed-off-by: Mauro Carvalho Chehab

[media] v4l: Add multi-planar API definitions to the V4L2 API

2011-03-21T23:31:33+00:00

Multi-planar API is as a backwards-compatible extension of the V4L2 API,
which allows video buffers to consist of one or more planes. Planes are
separate memory buffers; each has its own mapping, backed by usually
separate physical memory buffers.

Many different uses for the multi-planar API are possible, examples
include:
- embedded devices requiring video components to be placed in physically
separate buffers, e.g. for Samsung S3C/S5P SoC series' video codec,
Y and interleaved Cb/Cr components reside in buffers in different
memory banks;
- applications may receive (or choose to store) video data of one video
buffer in separate memory buffers; such data would have to be temporarily
copied together into one buffer before passing it to a V4L2 device;
- applications or drivers may want to pass metadata related to a buffer and
it may not be possible to place it in the same buffer, together with video
data.

[mchehab@redhat.com: CodingStyle fixes]
Signed-off-by: Pawel Osciak 
Signed-off-by: Kyungmin Park 
Reviewed-by: Marek Szyprowski 
Signed-off-by: Marek Szyprowski 
Reviewed-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab

[media] V4L2: Add seek spacing and RDS CAP bits

2010-10-21T09:55:58+00:00

Add spacing field to v4l2_hw_freq_seek.

Add V4L2_TUNER_CAP_RDS_BLOCK_IO, which indicates that the tuner/
transmitter if capable of transmitting/receiving RDS blocks.

Add V4L2_TUNER_CAP_RDS_CONTROLS capability, which indicates that the
RDS data is handled as values of predefined controls like radio text,
program ID and so on.

Signed-off-by: Matti J. Aaltonen 
Acked-by: Hans Verkuil 
Signed-off-by: Mauro Carvalho Chehab