linux-toradex.git/include/media/v4l2-dev.h, branch v3.0.44

[media] v4l: Fix media_entity_to_video_device macro argument name

2011-06-01T12:42:03+00:00

The name 'entity' is used twice in the macro body, once as the macro
argument, and once as a structure field name. This breaks compilation if
the macro is called with its argument not named 'entity'.

Fix this by renaming the macro argument '__e'. This should avoid
namespace clashes.

Signed-off-by: Laurent Pinchart 
Signed-off-by: Mauro Carvalho Chehab

[media] Revert "V4L/DVB: v4l2-dev: remove get_unmapped_area"

2011-05-20T15:14:40+00:00

This reverts commit c29fcff3daafbf46d64a543c1950bbd206ad8c1c.

Signed-off-by: Bob Liu 
Signed-off-by: Mauro Carvalho Chehab

[media] v4l2: use new flag to enable core priority handling

2011-03-22T19:38:16+00:00

Rather than guess which driver supports core priority handling, require drivers
that do to explicitly set the V4L2_FL_USE_FH_PRIO flag in video_device.

Updated the core prio handling accordingly and set the flag in the three
drivers that do.

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

[media] v4l2: add v4l2_prio_state to v4l2_device and video_device

2011-03-22T19:37:55+00:00

Integrate the v4l2_prio_state into the core, ready for use.

One struct v4l2_prio_state is added to v4l2_device and a pointer
to a prio state is added to video_device.

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

[media] v4l2_prio: move from v4l2-common to v4l2-dev

2011-03-22T19:37:54+00:00

We are going to move priority handling into the v4l2 core. As a consequence
the v4l2_prio helper functions need to be moved into the core videodev
module as well to prevent circular dependencies.

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

[media] v4l: Make video_device inherit from media_entity

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

V4L2 devices are media entities. As such they need to inherit from
(include) the media_entity structure.

When registering/unregistering the device, the media entity is
automatically registered/unregistered. The entity is acquired on device
open and released on device close.

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

[media] v4l: subdev: Add device node support

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

Create a device node named subdevX for every registered subdev.

As the device node is registered before the subdev core::s_config
function is called, return -EGAIN on open until initialization
completes.

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

V4L/DVB: v4l2: add core serialization lock

2010-10-21T03:06:14+00:00

Drivers can optionally set a pointer to a mutex in struct video_device.
The core will use that to lock before calling open, read, write, unlocked_ioctl,
poll, mmap or release.

Updated the documentation as well and ensure that v4l2-event knows about the
lock: it will unlock it before doing a blocking wait on an event and relock it
afterwards.

Ensure that the 'video_is_registered' check is done when the lock is held:
a typical disconnect will take the lock as well before unregistering the
device nodes, so to prevent race conditions the video_is_registered check
should also be done with the lock held.

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

V4L/DVB: v4l2-dev: remove get_unmapped_area

2010-10-21T03:06:14+00:00

The get_unmapped_area file operation is unused. Remove.

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

V4L/DVB: videotext: remove this obsolete API

2010-10-21T03:05:48+00:00

Remove the vtx (aka videotext aka teletext) API from the v4l2 core.
This API was scheduled for removal in kernel 2.6.35.

The vtx device nodes have been superseded by vbi device nodes
for many years. No applications exist that use the vtx support.
Of the two i2c drivers that actually support this API the saa5249
has been impossible to use for a year now and no known hardware
that supports this device exists. The saa5246a is theoretically
supported by the old mxb boards, but it never actually worked.

In summary: there is no hardware that can use this API and there
are no applications actually implementing this API.

The vtx support still reserves minors 192-223 and we would really
like to reuse those for upcoming new functionality. In the unlikely
event that new hardware appears that wants to use the functionality
provided by the vtx API, then that functionality should be build
around the sliced VBI API instead.

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