- 23 Mar, 2013 36 commits
-
-
Frank Schaefer authored
Previously, this has been done implicitly for video device nodes by calling set_input() (which calls audio_input() and also modified the mute setting). Since input and mute setting are now untangled (as much as possible), we need to apply the mute setting with an explicit call to audio_mute(). Also apply the mute setting when the radio device node gets opened. Signed-off-by:
Frank Schäfer <fschaefer.oss@googlemail.com> Acked-by:
Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
Frank Schaefer authored
Signed-off-by:
-
Frank Schaefer authored
Split function audio_mux(): move the mute setting part to function audio_mute() and the input setting part to function audio_input(). Signed-off-by:
-
Frank Schaefer authored
Move the GPIO part of function audio_mux() to a separate function audio_mux_gpio(). This prepares the code for the next patch which will separate mute and input setting. Signed-off-by:
-
Frank Schaefer authored
'audio_input' better describes the meaning of this field. Signed-off-by:
-
Frank Schaefer authored
We can't and do not save the mute setting in function audio_mux(), so we should also not save the input in this function for consistency. Signed-off-by:
-
Frank Schaefer authored
There are cases where we want to call audio_mux() without changing the value of the v4l2 mute control, for example - mute mute on last close - mute on device probing Signed-off-by:
-
Frank Schaefer authored
[media] bttv: audio_mux(): use a local variable "gpio_mute" instead of modifying the function parameter "mute" Function audio_mux() actually deals with two types of mute: gpio mute and subdevice muting. This patch claryfies the meaning of these values, but mainly prepares the code for the next patch. Signed-off-by:
-
Wei Yongjun authored
In case of error, the function clk_get() returns ERR_PTR() and never returns NULL. The NULL test in the return value check should be replaced with IS_ERR(). Signed-off-by:
Wei Yongjun <yongjun_wei@trendmicro.com.cn> Acked-by:
Lad, Prabhakar <prabhakar.csengg@gmail.com> Reviewed-by:
Sakari Ailus <sakari.ailus@iki.fi> Signed-off-by:
-
David Härdeman authored
store_protocols() treats dev->rc_map.rc_type as a bitmap which is wrong for two reasons. First of all, it is pretty bogus to change the protocol type of the keymap just because the hardware has been asked to decode a different protocol. Second, dev->rc_map.rc_type is an enum (i.e. a single protocol) as pointed out by James Hogan <james.hogan@imgtec.com>. Fix both issues by introducing a separate enabled_protocols member to struct rc_dev. Signed-off-by:
David Härdeman <david@hardeman.nu> Signed-off-by:
-
Sachin Kamat authored
ts2020.h was included twice. Signed-off-by:
Sachin Kamat <sachin.kamat@linaro.org> Signed-off-by:
-
Jose Alberto Reguero authored
This patch enable dual tuner for Avermedia Twinstar. Signed-off-by:
Jose Alberto Reguero <jareguero@telefonica.net> Signed-off-by:
-
Hans Verkuil authored
The dv_preset API is deprecated and is replaced by the much improved dv_timings API. Remove the dv_preset support from this driver as this will allow us to remove the dv_preset API altogether (s5p-tv being the last user of this code). Signed-off-by:
Tomasz Stanislawski <t.stanislaws@samsung.com> Acked-by:
-
Hans Verkuil authored
The dv_preset API is deprecated and is replaced by the much improved dv_timings API. Remove the dv_preset support from this driver as this will allow us to remove the dv_preset API altogether (s5p-tv being the last user of this code). Signed-off-by:
-
Hans Verkuil authored
The dv_preset API is deprecated and is replaced by the much improved dv_timings API. Remove the dv_preset support from this driver as this will allow us to remove the dv_preset API altogether (s5p-tv being the last user of this code). Signed-off-by:
-
Hans Verkuil authored
This just adds dv_timings support without modifying existing dv_preset support. Signed-off-by:
-
Hans Verkuil authored
This just adds dv_timings support without modifying existing dv_preset support. Signed-off-by:
-
Hans Verkuil authored
This just adds dv_timings support without modifying existing dv_preset support, although I had to refactor a little bit in order to share hdmiphy_find_conf() between the preset and timings code. Signed-off-by:
-
Wei Yongjun authored
usb_free_coherent() is safe with NULL addr and this check is not required. Signed-off-by:
-
Jean Delvare authored
Last parameter of function GetLockStatus() isn't used so drop it. Signed-off-by:
Jean Delvare <khali@linux-fr.org> Signed-off-by:
-
Lad, Prabhakar authored
export the symbols which are used by two modules vpif_capture and vpif_display. renamed "ch_params" to "vpif_ch_params" so as to avoid name collision. This patch fixes following error: ERROR: "ch_params" [drivers/media/platform/davinci/vpif_display.ko] undefined! ERROR: "vpif_ch_params_count" [drivers/media/platform/davinci/vpif_display.ko] undefined! ERROR: "vpif_base" [drivers/media/platform/davinci/vpif_display.ko] undefined! ERROR: "ch_params" [drivers/media/platform/davinci/vpif_capture.ko] undefined! ERROR: "vpif_ch_params_count" [drivers/media/platform/davinci/vpif_capture.ko] undefined! ERROR: "vpif_base" [drivers/media/platform/davinci/vpif_capture.ko] undefined! make[1]: *** [__modpost] Error 1 Reported-by:
Sekhar Nori <nsekhar@ti.com> Signed-off-by:
-
Chen Gang authored
for NUL terminated string, need always set 0 in the end. Signed-off-by:
Chen Gang <gang.chen@asianux.com> Signed-off-by:
-
Eduardo Valentin authored
Add MODULE_ALIAS entry for radio-si4713 platform driver. Signed-off-by:
Eduardo Valentin <edubezval@gmail.com> Acked-by:
-
Eduardo Valentin authored
Simple addition of platform_driver->driver->owner for radio-si4713. Signed-off-by:
-
Eduardo Valentin authored
As per code header comment, changing the driver license entry to match the correct version. Signed-off-by:
-
Eduardo Valentin authored
Minor changes to make alignment match on open parenthesis. Signed-off-by:
-
Antti Palosaari authored
I just made commit: "dvb_usb_v2: rework USB streaming logic" that breaks that driver PID filter. it913x driver checks use of PID filter directly from DVB USB v2 core internal variable "adap->pid_filtering" and stores it to own state. Calling order of .pid_filter_ctrl() and .pid_filter() was changed and due to that state was updated too late. Update state earlier. TODO: checking PID filter usage from DVB USB v2 is not very good idea as PID filter callbacks are called only when PID filter is enabled. Signed-off-by:
Antti Palosaari <crope@iki.fi> Signed-off-by:
-
Antti Palosaari authored
Control flow order changed a little bit. HW PID filter is now disabled also when streaming is stopped - earlier it was just set only when streaming was started. Control flow is now: * set streaming status bit * submit USB streaming packets * enable HW PID filter * ask device to start streaming * N x add PID to device HW PID filter ... streaming video ... * N x remove PID from device HW PID filter * ask device to stop streaming * disable HW PID filter * kill USB streaming packets * clear streaming status bit Signed-off-by:
-
Antti Palosaari authored
New checkpatch version likes to see strings not to split multiple lines even those are exceeding 80 line length. Signed-off-by:
-
Antti Palosaari authored
New checkpatch version likes to see strings not to split multiple lines even those are exceeding 80 line length. Signed-off-by:
-
Antti Palosaari authored
There was sync mutex which was held over userspace. That is very wrong and could cause deadlock if different userspace process is used to "unlock". Wait queue seems to be correct solution for that kind of synchronizing issue so use it instead. lock debug gives following bug report: ================================================ [ BUG: lock held when returning to user space! ] 3.9.0-rc1+ #38 Tainted: G O ------------------------------------------------ tzap/4614 is leaving the kernel with locks still held! 1 lock held by tzap/4614: Signed-off-by:
-
Mauro Carvalho Chehab authored
Instead of checking everywhere there for 3 symbols, use instead IS_ENABLED macro. Signed-off-by: -
Mauro Carvalho Chehab authored
Instead of checking everywhere there for 3 symbols, use instead IS_ENABLED macro. Signed-off-by: -
Mauro Carvalho Chehab authored
Instead of checking everywhere there for 3 symbols, use instead IS_ENABLED macro. Signed-off-by: -
Mauro Carvalho Chehab authored
Instead of checking everywhere there for 3 symbols, use instead IS_ENABLED macro. Signed-off-by: -
Mauro Carvalho Chehab authored
As reported by Geert Uytterhoeven <geert@linux-m68k.org>: drivers/media/usb/hdpvr/hdpvr-video.c: warning: "CONFIG_I2C_MODULE" is not defined [-Wundef] Reported-by:
Geert Uytterhoeven <geert@linux-m68k.org> Thanks-to: Randy Dunlap <rdunlap@infradead.org> Signed-off-by:
-
- 22 Mar, 2013 4 commits
-
-
Wei Yongjun authored
dvb_usb_v2_generic_io() was not declared. It should be static. Signed-off-by:
-
Hans Verkuil authored
Commit aab3125c broke em28xx. I traced this eventually to the change in what algo_data points to. This pointer is also passed to em28xx_tuner_callback() through several hidden tuner layers (yuck!) and that callback was not updated. Signed-off-by:
-
Mauro Carvalho Chehab authored
There's currently a bug on em28xx-i2c that makes it write the wrong values to register 06, that controlls the I2C bus speed and bus. Fix it to change only the I2C bus flag. Signed-off-by: -
Mauro Carvalho Chehab authored
It used to be a code that returns arror at ov7660_init. However, this was removed by changeset c84e412f: @@ -231,33 +116,40 @@ int ov7660_init(struct sd *sd) if (dump_sensor) ov7660_dump_registers(sd); - err = ov7660_set_gain(&sd->gspca_dev, sensor_settings[GAIN_IDX]); - if (err < 0) - return err; + return 0; +} - err = ov7660_set_auto_white_balance(&sd->gspca_dev, - sensor_settings[AUTO_WHITE_BALANCE_IDX]); - if (err < 0) - return err; As complained by gcc: drivers/media/usb/gspca/m5602/m5602_ov7660.c: In function 'ov7660_init': drivers/media/usb/gspca/m5602/m5602_ov7660.c:99:9: warning: variable 'err' set but not used [-Wunused-but-set-variable] It should be noticed that the original error code was crappy, as it wasn't returning any error if sensor init fails. Fix it by returning an error if the sensor can't be initialized. Cc: Hans de Goede <hdegoede@redhat.com> Signed-off-by:
-
