- 23 Mar, 2013 13 commits
-
-
Eduardo Valentin authored
Simple addition of platform_driver->driver->owner for radio-si4713. Signed-off-by:
Eduardo Valentin <edubezval@gmail.com> Acked-by:
Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
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 7 commits
-
-
Wei Yongjun authored
dvb_usb_v2_generic_io() was not declared. It should be static. Signed-off-by:
Wei Yongjun <yongjun_wei@trendmicro.com.cn> Acked-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:
-
Mauro Carvalho Chehab authored
This field is unused. Remove it. Signed-off-by: -
Mauro Carvalho Chehab authored
Changeset 8f3741e0 accidentally broke the CNR estimation. It should be calculated as "a + b - c". However, previously, the subtraction by c only occurred if SNR would be positive, due to a bad binding to DVBv3 API. This also fixes the following warning: drivers/media/dvb-frontends/drxk_hard.c:2556:6: warning: variable 'c' set but not used [-Wunused-but-set-variable] Signed-off-by:
-
Mauro Carvalho Chehab authored
As reported by Frank Schäfer <fschaefer.oss@googlemail.com>: ERROR: "__divdi3" [drivers/media/common/siano/smsdvb.ko] undefined! Reported-by:
Frank Schäfer <fschaefer.oss@googlemail.com> Tested-by:
Gianluca Gennari <gennarone@gmail.com> Signed-off-by:
-
- 21 Mar, 2013 20 commits
-
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
Use more careful error checks. Signed-off-by:
-
Antti Palosaari authored
Use register address auto increment to reduce I/O when large register / values tables are written. Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
That register is property of demodulator so move it correct place. Signed-off-by:
-
Antti Palosaari authored
Those are demodulator init tables according to used tuner tuner config. af9033 demod driver does those inits currently and due to that these duplicate inits could be removed. Signed-off-by:
-
Antti Palosaari authored
Dumped out from the Windows driver version 12.07.06.1 Signed-off-by:
-
Antti Palosaari authored
Dumped out from the Windows driver version 12.07.06.1 Signed-off-by:
-
Antti Palosaari authored
Dumped out from the Windows driver version 12.07.06.1 Signed-off-by:
-
Antti Palosaari authored
Dumped out from the Windows driver version 12.07.06.1 Signed-off-by:
-
Antti Palosaari authored
Dumped out from the Windows driver version 12.07.06.1 Signed-off-by:
-
Antti Palosaari authored
Dumped out from the Windows driver version 12.07.06.1 Signed-off-by:
-
Antti Palosaari authored
For some reason there seems to be value 0x03 in eeprom for dual mode (and 0x00 for single mode). Boolean is not always 1 bit wide - it could be 8 bit wide too. Storing number 0x03 to boolean causes driver to thing there is 4 tuners in some cases :o Add also some comments regarding to eeprom. Signed-off-by:
-
Antti Palosaari authored
There is no difference towards AF9035 remote controller, so enable it. Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
eeprom memory mapped base address is detected at the very first. Use it everywhere. Signed-off-by:
-
Antti Palosaari authored
AF9035 and IT9135 supports two different firmware format. Select correct loader according to first byte of firmware file. Signed-off-by:
-
Antti Palosaari authored
These are demod inits and are already done by af9033 demod driver. Signed-off-by:
-
Antti Palosaari authored
Dumped out from Windows driver version 12.07.06.1, 07/06/2012. Signed-off-by:
-
