- 05 Dec, 2009 40 commits
-
-
Mike Isely authored
Signed-off-by:
Mike Isely <isely@pobox.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
Mike Isely authored
The driver also contains a piece of configuration data that produces a one line description of the specific hardware being driver (e.g. "Hauppauge 24xxx", "OnAir", etc). This change generates an informational message to the kernel log reporting the hardware type being driven. This is a very useful thing to know when diagnosing problems. Signed-off-by:
-
Mike Isely authored
It used to be that the only real detectable reason for the driver to fail during initialization would be that if the hardware is simply jammed. However with the advent of the sub-device mechanism in V4L it is possible now to detect if a sub-device module fails to load successfully. The pvrusb2 driver does in fact react to this by also (correctly) failing, however the original diagnostic message "hardware is jammed" was still being reported. This misleads the user because in fact it might not actually be a hardware failure. This change adds logic to tell the difference and then report a more appropriate message to the kernel log. Signed-off-by:
-
Mike Isely authored
pvrusb2: Encoder failures are mostly recoverable by the driver. While it would sure be nice not to have the failure happen in the first place, this has been going on for years and I doubt that a real solution will ever present itself. I think that part's firmware is just slightly flakey and we have to deal with it. The driver does deal with it just fine, but the warning message going into the kernel log is probably a little more alarming than it should be. So try to soften up the warning somewhat. Signed-off-by:
-
Mike Isely authored
pvrusb2: Associate V4L device node in sysfs with the underlying USB device. This opens the door to device information tracking in udev Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
Michael Krufky <mkrufky@kernellabs.com> Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
consolidate common code used to determine if calibration on startup is needed Signed-off-by:
-
Michael Krufky authored
If rf_cal_on_startup is enabled in the structure passed into tda18271_attach, and the cal module option isn't disabled, then we should run the initialization and calibration procedures during the tda18271_attach function call, regardless of how many instances of the driver have been attached. If the device is already calibrated, the driver will detect that and will only calibrate again if necessary. Signed-off-by:
-
Michael Krufky authored
If rf_cal_on_startup is enabled in the structure passed into tda18271_set_config, and the cal module option isn't disabled, then we should run the initialization and calibration procedures during the tda18271_set_config function call. Signed-off-by:
-
Michael Krufky authored
Add the set_config method to allow drivers to configure the tda18271 driver options after attach. Signed-off-by:
-
Michael Krufky authored
There is already an option for sending 16 byte chunks rather that writing 39 bytes all at once during the tuner's initialization. Some i2c buses can't send 16 bytes at once, so create an option for sending 8 byte chunks. Signed-off-by:
-
David T.L. Wong authored
Signed-off-by:
David T.L. Wong <davidtlwong@gmail.com> Signed-off-by:
-
David T.L. Wong authored
Signed-off-by:
-
David T.L. Wong authored
Signed-off-by:
-
David T.L. Wong authored
Signed-off-by:
-
David T.L. Wong authored
Signed-off-by:
-
David T.L. Wong authored
Signed-off-by:
-
David T.L. Wong authored
Signed-off-by:
-
Michael Krufky authored
Thanks to Terry Wu for finding the GPIOs required for svideo / composite input Cc: Terry Wu <terrywu2009@gmail.com> Signed-off-by:
-
Michael Krufky authored
Enable the standby mode optimization to disable the tda18271 slave tuner output / loop thru options when in low power mode on the slave tuner, only. The master tuner must always leave slave tuner output / loop thru enabled. Signed-off-by:
-
Jean-Francois Moine authored
Signed-off-by:
Jean-Francois Moine <moinejf@free.fr> Signed-off-by:
-
Amauri Magagna authored
- set correct colors at startup time - autogain was too slow (4-5 mn - now 15-30 s)) Signed-off-by:
Amauri Magagna <amaurimagagna@gmail.com> Signed-off-by:
-
Olivier Lorin authored
- add flip/mirror support for OV2640 - fix for backlight value range - fix for red-blue inversion hue mode with V4L1 applications Signed-off-by:
Olivier Lorin <o.lorin@laposte.net> Signed-off-by:
-
Olivier Lorin authored
- small changes in comments - unified naming scheme for subdriver variables Signed-off-by:
-
Olivier Lorin authored
- fix for warning compilation about sd_ctrls - trace improvement while probing the sensor Signed-off-by:
-
Jean-Francois Moine authored
Signed-off-by:
-
Marton Nemeth authored
The original implementation of pac_find_sof() does not always find the Start Of Frame (SOF) marker. Replace it with a state machine based design. Acked-by:
Hans de Goede <hdegoede@redhat.com> Signed-off-by:
Marton Nemeth <nm127@freemail.hu> Signed-off-by:
-
Devin Heitmueller authored
Xc5000 tuning attempts shouldn't return zero in the case where the firmware did not load successfully. Thanks to Michael Krufky for pointing out this issue. Cc: Michael Krufky <mkrufky@kernellabs.com> Signed-off-by:
Devin Heitmueller <dheitmueller@kernellabs.com> Signed-off-by:
-
Devin Heitmueller authored
Add support for saturation/hue controls, prompted by errors showing up in the mythbackend log. Signed-off-by:
-
Hans de Goede authored
gspca: Don't resubmit error status URB's when suspending Signed-off-by:
-
Hans de Goede authored
The gscpa core was not resubmitting URB's when the URB status was an error, this means we will loose URB's (potentially all stopping the stream) in case of sporadic USB issues. I've seen this with an Aiptek stv0680 based PenCam connected through an USB 2.0 hub. Signed-off-by:
-
Hans de Goede authored
This patch adds a new subdriver to gspca supporting cams with the stv0680 bridge (replacing the old in kernel v4l1 driver). Many thanks to Hans Verkuil for providing me with one of the 2 cams used in testing this new sub driver. Signed-off-by:
-
Hans de Goede authored
gspca w9968cf: slight tweak to vstart and hstart to get rid of black borders in 640x480 mode. Signed-off-by:
-
Hans de Goede authored
gspca w9968cf: Add support for JPEG compression, this enables much higher framerates at 320x240 / 352x288 and also allows for 640x480 mode for cams which can do this. The w9968cf uses planar JPEG, which libv4l until now did not support, so this requires atleast version 0.6.3 of libv4l. And something important I forgot to mention in my earlier w9968cf commits: Many thanks to Hans Verkuil for giving me a w9968cf based cam, which has allowed me to develop the gspca w9968cf support. Signed-off-by:
-
Hans de Goede authored
gspca-w9968cf: Don't add an extra packet to the buffer after the EOF, this makes the frame data size bigger then it should be which makes gstreamer discard it. This patch also fixes an unrelated compiler warning. Signed-off-by:
-
Hans de Goede authored
Cache sensor regs to avoid unnecessary slow i2c reads / writes, this speeds up sd_start a bit with most bridges and a lot (from 5 seconds down to 0.3 seconds) with W996xCF cams, as this avoids very slow bit bang IO over USB i2c reads. Signed-off-by:
-
Hans de Goede authored
This patch adds support to gspca for the Winbond W9967CF and W9968CF camera's. This is mostly a port of the existing v4l1 driver to gspca (making it v4l2). But this also features fixes to the bitbanging i2c code (send a nack not an ack after reading the last byte of a transfer), which gets rid of the weird errors which were being seen there, and of the smbus_refresh() hack to get around these errors. Also the vstart settings have been tweaked to work with different frequency filter settings. Signed-off-by:
-
Richard Röjfors authored
This patch adds support for TEF6862 Car Radio Enhanced Selectivity Tuner. It's implemented as a subdev, supporting checking signal strength and setting and getting frequency. Signed-off-by:
Richard Röjfors <richard.rojfors@mocean-labs.com> Signed-off-by:
-
Richard Röjfors authored
If the I2C device provides an interrupt it is registered and the standard is updated via interrupts rather than polling. Since I2C communication is needed, the interrupt handler fires off a work which will check the new standard, and store it in the internal structure. To handle mutual exclusion a mutex is introduced. Signed-off-by:
-
