- 19 May, 2010 40 commits
-
-
Hans Verkuil authored
Signed-off-by:
Hans Verkuil <hverkuil@xs4all.nl> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
Sakari Ailus authored
Add documentation on how to use V4L2 events, both for V4L2 drivers and for V4L2 applications. Signed-off-by:
Sakari Ailus <sakari.ailus@maxwell.research.nokia.com> Signed-off-by:
-
Sakari Ailus authored
Add support for event handling to do_ioctl. Signed-off-by:
-
Sakari Ailus authored
Add event handling backend to V4L2. The backend handles event subscription and delivery to file handles. Event subscriptions are based on file handle. Events may be delivered to all subscribed file handles on a device independent of where they originate from. Signed-off-by:
-
Sakari Ailus authored
This patch adds a set of new ioctls to the V4L2 API. The ioctls conform to V4L2 Events RFC version 2.3: <URL:http://www.spinics.net/lists/linux-media/msg12033.html> Signed-off-by:
-
Sakari Ailus authored
Add documentation on using V4L2 file handles (v4l2_fh) in V4L2 drivers. Signed-off-by:
-
Sakari Ailus authored
This patch adds a list of v4l2_fh structures to every video_device. It allows using file handle related information in V4L2. The event interface is one example of such use. The use of v4l2_fh is not mandatory for drivers. Signed-off-by:
-
Pawel Osciak authored
This is a virtual device driver for testing the memory-to-memory framework. This virtual device uses in-memory buffers for both its source and destination. It is capable of multi-instance, multi-buffer-per-transaction operation (via the mem2mem framework). [mchehab@redhat.com: use videobuf_queue_to_vaddr instead of the removed videobuf_queue_to_vmalloc] Signed-off-by:
Pawel Osciak <p.osciak@samsung.com> Signed-off-by:
Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Reviewed-by:
Vaibhav Hiremath <hvaibhav@ti.com> Tested-by:
-
Pawel Osciak authored
A mem-to-mem device is a device that uses memory buffers passed by userspace applications for both their source and destination data. This is different from existing drivers, which utilize memory buffers for either input or output, but not both. In terms of V4L2 such a device would be both of OUTPUT and CAPTURE type. Examples of such devices would be: image 'resizers', 'rotators', 'colorspace converters', etc. This patch adds a separate Kconfig sub-menu for mem-to-mem devices as well. Signed-off-by:
-
Xiaolin Zhang authored
Add support for more color effects (negative, sketch, emboss, etc) by extending the v4l2_colorfx enum items. Signed-off-by:
Xiaolin Zhang <xiaolin.zhang@intel.com> Signed-off-by:
-
Guennadi Liakhovetski authored
AK8814 only differs from AK8813 by included Macrovision Copy Protection function. This patch adds a driver for AK8813 and AK8814 I2C PAL/NTSC TV encoders. Signed-off-by:
Guennadi Liakhovetski <g.liakhovetski@gmx.de> Signed-off-by:
-
Guennadi Liakhovetski authored
A number of SuperH Mobile SoCs, including sh7724, include a Video Output Unit. This patch adds a video (V4L2) output driver for it. The driver uses v4l2-subdev and mediabus APIs to interface to TV encoders. Signed-off-by:
Paul Mundt <lethal@linux-sh.org> Signed-off-by:
-
Guennadi Liakhovetski authored
Signed-off-by:
-
Guennadi Liakhovetski authored
Signed-off-by:
-
Guennadi Liakhovetski authored
soc-camera no longer requires .set_crop() implementations to update their argument. Update the commentary. Signed-off-by:
-
Guennadi Liakhovetski authored
Current version of sh_mobile_ceu_camera.c interprets the V4L2 API specification of the VIDIOC_S_CROP ioctl as "change input (for capture devices) area, preserve scaling factors, therefore change output window," whereas a more intuitive interpretation of the API is "change input area, preserve output window." Switch sh_mobile_ceu_camera.c to use this interpretation. Signed-off-by:
-
Hans Verkuil authored
- Clean up the code - Use the kernel's built-in vga8x16 font instead of our own. - Drop exclusive open: now multiple users can open the device as per the V4L2 spec. - Move the format description to the vivi device instead of keeping it in the file handle. Again as per the spec. - Streamline and simplify the drawing code. It is now easy to add text on top of the colorbar pattern. - Upgrade the max resolution to 1920x1200. Signed-off-by:
-
Mauro Carvalho Chehab authored
drivers/media/video/videobuf-dma-sg.c: In function ‘__videobuf_mmap_mapper’: drivers/media/video/videobuf-dma-sg.c:557: warning: ‘size’ may be used uninitialized in this function The condition where size is floating should never happen, due to the paranoia check, but a future change at the logic might break it. So, let's just set size to zero and use it for the paranoia check. Signed-off-by: -
Jean-François Moine authored
Signed-off-by:
Jean-François Moine <moinejf@free.fr> Signed-off-by:
-
Jean-François Moine authored
Signed-off-by:
-
Jean-François Moine authored
Signed-off-by:
-
Hans Verkuil authored
mmap_mapper should operate on a buffer, not on a complete queue. So let the videobuf-core find the correct buffer instead of duplicating that code in each mmap_mapper implementation. The dma-sg implementation has backwards compatibility code for handling the V4L1_COMPAT layer. This code is now under the v4L1_COMPAT config option. Signed-off-by:
-
Hans Verkuil authored
The video_copy_to_user and copy_stream ops are almost identical for all videobuf memtype variants. All that is needed is to use the new vaddr op and these functions can be moved into the core, ensuring we have just one single implementation instead of three. Signed-off-by:
-
Hans Verkuil authored
Ths function returns the virtual kernel address of the buffer and has nothing to do with allocation. Signed-off-by:
-
Hans Verkuil authored
Rename the .vmalloc op in struct videobuf_qtype_ops to .vaddr. This op returns the virtual kernel address of a buffer. vaddr is a lot less confusing than vmalloc since this callback does do any allocations. Signed-off-by:
-
Hans Verkuil authored
videobuf_alloc() returned a void *. Change to struct videobuf_buffer * to get better type checking. Signed-off-by:
-
Hans Verkuil authored
Thanks to Pawel Osciak for noticing this. Signed-off-by:
-
Hans Verkuil authored
Remove the mmap_free callback from struct videobuf_qtype_ops. All implementations of this callback do the same trivial check: return -EBUSY if any buffer is mmapped. That can also be tested in the videobuf core. Signed-off-by:
-
Hans Verkuil authored
The mmap callback in struct videobuf_qtype_ops is never used. Remove. Signed-off-by:
-
Mauro Carvalho Chehab authored
From: Stefan Ringel <stefan.ringel@arcor.de> The firmware were seen to be needed with some tm6000 devices that don't work with version 2.7. Thanks-to: Bee Hock Goh <beehock@gmail.com> Signed-off-by:
Stefan Ringel <stefan.ringel@arcor.de> Signed-off-by:
-
Mauro Carvalho Chehab authored
Patch reverted per Andreas Oberritter <obi@linuxtv.org> request. It is basically not ready yet for upstream merge. This reverts commit 77b2ad374a82e3d740cb1780ff4caedc3e051b37. Signed-off-by: -
Dean Anderson authored
Signed-off-by:
Dean Anderson <linux-dev@sensoray.com> Signed-off-by:
-
Klaus Schmidinger authored
The enum fe_caps provides flags that allow an application to detect whether a device is capable of handling various modulation types etc. A flag for detecting PSK_8, however, is missing. This patch adds the flag FE_CAN_PSK_8 to frontend.h and implements it for the gp8psk-fe.c and cx24116.c driver (apparently the only ones with PSK_8). Only the gp8psk-fe.c has been explicitly tested, though. Signed-off-by:
Klaus Schmidinger <Klaus.Schmidinger@tvdr.de> Tested-by:
Derek Kelly <user.vdr@gmail.com> Acked-by:
Manu Abraham <manu@linuxtv.org> Signed-off-by:
-
David Härdeman authored
Fix some confusing comments in drivers/media/IR/* Signed-off-by:
David Härdeman <david@hardeman.nu> Signed-off-by:
-
Mauro Carvalho Chehab authored
drivers/media/IR/ir-keytable.c would alloc a suitably sized keymap table only to have it resized as it is populated with the initial keymap. Signed-off-by:
-
David Härdeman authored
Fix a double initialization of the same spinlock in drivers/media/IR/rc-map.c. Signed-off-by:
-
David Härdeman authored
Convert drivers/media/dvb/dm1105/dm1105.c to not rely on ir-functions.c. Signed-off-by:
-
Mauro Carvalho Chehab authored
Driver is not properly initializing u64 constants on 32 bit systems: drivers/media/IR/imon.c:301: warning: integer constant is too large for ‘long’ type drivers/media/IR/imon.c:302: warning: integer constant is too large for ‘long’ type drivers/media/IR/imon.c:304: warning: integer constant is too large for ‘long’ type drivers/media/IR/imon.c:305: warning: integer constant is too large for ‘long’ type drivers/media/IR/imon.c:308: warning: integer constant is too large for ‘long’ type drivers/media/IR/imon.c:309: warning: integer constant is too large for ‘long’ type drivers/media/IR/imon.c:310: warning: integer constant is too large for ‘long’ type Fix also a few troubles at error printk handling: drivers/media/IR/imon.c: In function ‘imon_init_intf0’: drivers/media/IR/imon.c:1909: warning: ‘ret’ may be used uninitialized in this function drivers/media/IR/imon.c: In function ‘imon_init_intf1’: drivers/media/IR/imon.c:1989: warning: ‘ret’ may be used uninitialized in this function Cc: Jarod Wilson <jarod@redhat.com> Signed-off-by: -
David Härdeman authored
This patch adds a Sony12/15/20 decoder to ir-core. Signed-off-by:
-
David Härdeman authored
This patch adds a JVC decoder to ir-core. Signed-off-by:
-
