- 08 Nov, 2011 20 commits
-
-
Sylwester Nawrocki authored
Fixes following checkpatch.pl warning: WARNING: externs should be avoided in .c files Cc: Devin Heitmueller <dheitmueller@kernellabs.com> Signed-off-by:
Sylwester Nawrocki <snjw23@gmail.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
Sylwester Nawrocki authored
Cc: Devin Heitmueller <dheitmueller@kernellabs.com> Signed-off-by:
-
Sylwester Nawrocki authored
The as10x_cmd.h header is not public so there should be no need for an "extern "C"" in it. Cc: Devin Heitmueller <dheitmueller@kernellabs.com> Signed-off-by:
-
Sylwester Nawrocki authored
While at it also correct some spelling errors. Cc: Devin Heitmueller <dheitmueller@kernellabs.com> Signed-off-by:
-
Sylwester Nawrocki authored
Remove some unnecessary braces. Replace spaces with tabs where expected. Replace gcc specific __FUNCTION__ with C99 __func__. No functional changes. Cc: Devin Heitmueller <dheitmueller@kernellabs.com> Signed-off-by:
-
Sylwester Nawrocki authored
Release already acquired resources when error happens during devices registration steps. Use dev_err() where struct device is available, instead of driver specific err(). Cc: Devin Heitmueller <dheitmueller@kernellabs.com> Signed-off-by:
-
Sylwester Nawrocki authored
Cc: Devin Heitmueller <dheitmueller@kernellabs.com> Signed-off-by:
Piotr Chmura <chmooreck@poczta.onet.pl> Signed-off-by:
-
Sylwester Nawrocki authored
It doesn't seem to be of much advantage to compile in FW_LOADER support conditionally, then make the driver always select FW_LOADER and remove #idefs from the code. Cc: Devin Heitmueller <dheitmueller@kernellabs.com> Signed-off-by:
-
Sylwester Nawrocki authored
SPI bus driver support is not included in this module, the SPI driver files are missing. But some bits are still present so clean up the unused code. The SPI driver support can be properly added later if needed. Then CONFIG_AS102_SPI and CONFIG_AS102_USB is now not needed and the pre-processor statements using these config options can now be removed from *.c files. Cc: Devin Heitmueller <dheitmueller@kernellabs.com> Signed-off-by:
-
Sylwester Nawrocki authored
According to the kernel coding rules typedefs should be avoided, so replace theit occurances with explicit enum/union types. Cc: Devin Heitmueller <dheitmueller@kernellabs.com> Signed-off-by:
-
Piotr Chmura authored
Cc: Devin Heitmueller <dheitmueller@kernellabs.com> Signed-off-by:
-
Malcolm Priestley authored
Correction of reading from frontend and represents a SNR nonlinear scale of minimum signal to full signal. Signed-off-by:
Malcolm Priestley <tvboxspy@gmail.com> Signed-off-by:
-
Peter De Schrijver authored
add support for conexant PCI device 0x36c. Seems to be fully compatible with the currently supported chips, yet the chip has different PCI ID. Signed-off-by:
Peter De Schrijver <p2@psychaos.be> Signed-off-by:
-
Peter De Schrijver authored
The following patch adds support for the Tongwei Video Technology TD-3116 board. This is a Bt878 based capture card with 16 inputs meant for surveilance applications. It also offers a way to check which inputs have a video signal while capturing another input. In addition there are a number of alarm inputs and outputs available and there is microcontroller which is presumably intended for use as a system watchdog. None of these extra capabilities are supported by the patch. Signed-off-by:
-
Malcolm Priestley authored
IT9135 devices do support USB 1. Support added with restricton on pid count to 5. IT9137 devices wil not connect in USB 1 mode. Signed-off-by:
-
Javier Martinez Canillas authored
64933337 [media] tvp5150: Add video format registers configuration values Added constants for each video standard supported by TVP5150, so this patch get rid of the magic numbers. Signed-off-by:
Javier Martinez Canillas <martinez.javier@gmail.com> Signed-off-by:
-
Kamil Debski authored
G2D is a 2D graphics accelerator engine present in the s5p family of Samsung SoCs. It is capable of bitblt and raster operations on images having dimensions of up to 8000x8000. Signed-off-by:
Kamil Debski <k.debski@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by:
Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by:
-
Michael Krufky authored
Reported-by:
Antti Palosaari <crope@iki.fi> Signed-off-by:
Michael Krufky <mkrufky@linuxtv.org> Signed-off-by:
-
Michael Krufky authored
Reported-by:
-
Michael Krufky authored
Reported-by:
-
- 07 Nov, 2011 20 commits
-
-
Josh Boyer authored
The ttusb2_msg function uses on-stack variables to submit commands to dvb_usb_generic. This eventually gets to the DMA api layer and will throw a traceback if the debugging options are set. This allocates the temporary buffer variables with kzalloc instead. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=734506Signed-off-by:
Josh Boyer <jwboyer@redhat.com> Signed-off-by:
-
tvboxspy authored
Amend adc table entries and size. Signed-off-by:
-
Malcolm Priestley authored
Support for version 2 type chips and other LNA versions of version 1 Scripts may be compressed slightly at a later stage. TODO Firmware loader However, things are a little confusing, it is not clear that dvb-usb-it9137-01.fw does not work with version 2 chips as in recent files both firmwares are the same. Should be applied to: 8133 Support for single ITE 9135 device. Signed-off-by:
-
Michael Krufky authored
As done first in lgdt330x.c, calculate signal strength from SNR up to 35dB Even though the SNR can go higher than 35dB, there is some comfort factor in having a range of strong signals that can show at 100% Signed-off-by:
Michael Krufky <mkrufky@kernellabs.com> Signed-off-by:
Devin Heitmueller <dheitmueller@kernellabs.com> Signed-off-by:
Steven Toth <stoth@kernellabs.com> Signed-off-by:
-
Michael Krufky authored
As done first in lgdt330x.c, calculate signal strength from SNR up to 35dB Even though the SNR can go higher than 35dB, there is some comfort factor in having a range of strong signals that can show at 100% Signed-off-by:
-
Michael Krufky authored
As done first in lgdt330x.c, calculate signal strength from SNR up to 35dB Even though the SNR can go higher than 35dB, there is some comfort factor in having a range of strong signals that can show at 100% Signed-off-by:
-
Julia Lawall authored
In the original code, probe_out could be reached when res was null and then when the irq had not yet been requested. In those cases, the call to free_irq is not needed, so move probe_out down and introduce a new label for the case where calling free_irq is useful. The semantic match that finds this problem is as follows: // <smpl> @r@ expression E, E1; identifier f; statement S1,S2,S3; @@ if (E == NULL) { ... when != if (E == NULL || ...) S1 else S2 when != E = E1 *E->f ... when any return ...; } else S3 // </smpl> Signed-off-by:Julia Lawall <julia@diku.dk> Signed-off-by:
-
Julia Lawall authored
The variable isi might be null or might be freed at the point of the call to clk_put. pclk contains the value that isi->pclk is expected to point to. The semantic match that finds this problem is as follows: // <smpl> @r@ expression E, E1; identifier f; statement S1,S2,S3; @@ if (E == NULL) { ... when != if (E == NULL || ...) S1 else S2 when != E = E1 *E->f ... when any return ...; } else S3 // </smpl> Signed-off-by: -
Christian Gmeiner authored
The ADV7170/ADV7171 can operate in either 8-bit or 16-bit YCrCb Mode. * 8-Bit YCrCb Mode This default mode accepts multiplexed YCrCb inputs through the P7-P0 pixel inputs. The inputs follow the sequence Cb0, Y0 Cr0, Y1 Cb1, Y2, etc. The Y, Cb and Cr data are input on a rising clock edge. * 16-Bit YCrCb Mode This mode accepts Y inputs through the P7–P0 pixel inputs and multiplexed CrCb inputs through the P15–P8 pixel inputs. The data is loaded on every second rising edge of CLOCK. The inputs follow the sequence Cb0, Y0 Cr0, Y1 Cb1, Y2, etc. Signed-off-by:
Christian Gmeiner <christian.gmeiner@gmail.com> Signed-off-by:
-
Dmitri Belimov authored
Write AUX byte to FM1216ME_MK3 when FM mode, better sensitivity. It can be usefull for other tuners. Signed-off-by:
Beholder Intl. Ltd. Dmitry Belimov <d.belimov@gmail.com> Signed-off-by:
-
Daniel Drake authored
The RGB mode does not work correctly. It captures fine at 640x480 but whenever the scaling engine is used to produce another resolution, color corruption occurs (lots of erroneous pink and green). It is not clear how the scaling engine is supposed to work and how it knows which pixel format it is dealing with. Work around this problem by disabling RGB support. YUYV scaling works just fine. Test case: gst-launch v4l2src ! video/x-raw-rgb,bpp=16,width=320,height=240 ! \ ffmpegcolorspace ! xvimagesink Signed-off-by:
Daniel Drake <dsd@laptop.org> Signed-off-by:
-
Mauro Carvalho Chehab authored
Re-run the cardlist script, in order to update the cardlists for a few drivers, to sync with the driver changes. Signed-off-by: -
sensoray-dev authored
commit affebd4db94b459f676a14d9bb696c3c2b73643d [media] bttv: adding Sensoray 611 board to bttv driver Signed-off-by:
Dean Anderson <linux-dev@sensoray.com> Signed-off-by:
-
sensoray-dev authored
commit cf5886c3dd2f65c817cb6ca5e7202fa3a3bdc872 Signed-off-by:
-
Laurent Pinchart authored
The MT9P031 and MT9T001 sensors transfer 16-bit data on the I2C bus in swapped order. Let the I2C core handle byte order by using the i2c_smbus_{read|write}_word_swapped() functions. Signed-off-by:Laurent Pinchart <laurent.pinchart@ideasonboard.com> Acked-by:
Jonathan Cameron <jic23@cam.ac.uk> Acked-by:
Jean Delvare <khali@linux-fr.org> Signed-off-by:
-
Archit Taneja authored
There is no limit to the number of displays that can registered with DSS2. The current value of MAX_DISPLAYS is 3, set this to 10 so that the 'displays' member of omap2video_device struct can store more omap_dss_device pointers. This fixes a crash seen in omap_vout_probe when DSS2 registers for more than 3 displays. Signed-off-by:
Archit Taneja <archit@ti.com> Acked-by:
Vaibhav Hiremath <hvaibhav@ti.com> Signed-off-by:
-
Archit Taneja authored
Add support for DSI panels. DSI video mode panels will work directly. For command mode panels, we will need to trigger updates regularly. This isn't done by the omap_vout driver currently. It can still be supported if we connect a framebuffer device to the panel and configure it in auto update mode. Signed-off-by:
-
Archit Taneja authored
Currently, in omap_vout_isr(), if the panel type is DPI, and if we get either VSYNC or VSYNC2 interrupts, we proceed ahead to set the current buffers state to VIDEOBUF_DONE and prepare to display the next frame in the queue. On OMAP4, because we have 2 LCD managers, the panel type itself is not sufficient to tell if we have received the correct irq, i.e, we shouldn't proceed ahead if we get a VSYNC interrupt for LCD2 manager, or a VSYNC2 interrupt for LCD manager. Fix this by correlating LCD manager to VSYNC interrupt and LCD2 manager to VSYNC2 interrupt. Signed-off-by:
Sumit Semwal <sumit.semwal@ti.com> Acked-by:
-
Archit Taneja authored
Currently, there is a lot of redundant code is between DPI and VENC panels, this can be made common by moving out field/interlace specific code to a separate function called omapvid_handle_interlace_display(). There is no functional change made. Signed-off-by:
-
Archit Taneja authored
The commit 383e4f69 makes reqbuf prevent requesting a larger size buffer than what is allocated at kernel boot during omap_vout_probe. In omap_vout_buffer_setup callback API, the requested size is compared with vout->buffer_size, this isn't correct as vout->buffer_size is later set to the size requested in reqbuf. When the video device is opened the next time, this check will prevent us to allocate a buffer which is larger than what we requested the last time. Don't use vout->buffer_size, always check with the parameters video1_bufsize or video2_bufsize. Signed-off-by:
-
