- 05 Dec, 2009 40 commits
-
-
Johann Friedrichs authored
In buffer_release() the previously allocated pagetables are not freed, which might result in a memory leak in certain application use-cases, where the frame format is changed from planar format to non-planar format. The fix explicitely frees the page tables when a format change is done and when buffer_release() is called. Signed-off-by:
Johann Friedrichs <johann.friedrichs@web.de> Signed-off-by:
Michael Hunold <hunold@linuxtv.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
Laurent Pinchart authored
Upcoming I2C v4l2_subdev drivers need a way to control the subdevice power state from the core. This use case is already partially covered by the tuner s_standby operation, but no way to explicitly come back from the standby state is available. Rename the tuner s_standby operation to core s_power, and fix tuner drivers accordingly. The tuner core will call s_power(0) instead of s_standby(). No explicit call to s_power(1) is required for tuners as they are supposed to wake up from standby automatically. [mchehab@redhat.com: CodingStyle fix] Signed-off-by:
Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by:
Hans Verkuil <hverkuil@xs4all.nl> Signed-off-by:
-
Jean Delvare authored
I do not think it makes sense any longer for ir-kbd-i2c to reject devices at unknown I2C addresses. The caller can provide all the details about how the device should be handled. Having to add new addresses to ir-kbd-i2c so that they aren't rejected is a pain we don't need. Unsupported devices will be spotted a few lines later anyway. This already lets us unlist 2 addresses (0x7a and 0x2d) for which handling details are always provided by the caller (saa7134-input). Hopefully we can remove more in the future. Signed-off-by:
Jean Delvare <khali@linux-fr.org> Signed-off-by:
-
Jean Delvare authored
Google is pretty clear that the HVR 1110 IR chip is always at address 0x71 and the BeholdTV IR chip is always at address 0x2d. This completes the list of IR device addresses for the SAA7134-based adapters, and we no longer need to probe any of them. Signed-off-by:
-
Jean Delvare authored
The i2c core prevents us from probing I2C address 0x7a because it's not a valid 7-bit address (reserved for 10-bit addressing.) So we must stop probing this address, and explicitly list all adapters which use it. Under the assumption that only the Upmost Purple TV adapter uses this invalid address, this fix should do the trick. Signed-off-by:
hermann pitton <hermann-pitton@arcor.de> Acked-by:
Jarod Wilson <jarod@redhat.com> Signed-off-by:
-
Jean Delvare authored
Recent fixes to the em28xx and saa7134 drivers have been overzealous. While the ir-kbd-i2c platform data indeed needs to be persistent, the struct i2c_board_info doesn't, as it is only used by i2c_new_device(). So revert a part of the original fixes, to save some memory. Signed-off-by:
-
Aleksandr V. Piskunov authored
cx25840: Disable 6.5MHz carrier autodetection for PAL, always assume its DK. Only try to autodetect 6.5MHz carrier for SECAM if user accepts both system DK and L. Signed-off-by:
Aleksandr V. Piskunov <alexandr.v.piskunov@gmail.com> Reviewed-by:
Andy Walls <awalls@radix.net> Signed-off-by:
-
Andy Shevchenko authored
Change own implementation of pwc_atoi() by simple_strtol(x, NULL, 10). Signed-off-by:
Andy Shevchenko <ext-andriy.shevchenko@nokia.com> Acked-by:
Pekka Enberg <penberg@cs.helsinki.fi> Signed-off-by:
-
Mike Isely authored
Signed-off-by:
Mike Isely <isely@pobox.com> Signed-off-by:
-
Mike Isely authored
After detecting failure due to module initialization error, get out. Don't report jammed hardware. Problem due to a missing break statement. Signed-off-by:
-
Mike Isely authored
Signed-off-by:
-
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:
-
