- 21 Mar, 2013 40 commits
-
-
Antti Palosaari authored
Signed-off-by:
Antti Palosaari <crope@iki.fi> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
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:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
We don't need it. Tuner ID and device address are enough. Signed-off-by:
-
Antti Palosaari authored
Copy forgotten power up registers from it913x-fe driver. Remove two demod registers as those are already written by af9033 driver. Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
Merge those functions to one and disable sleep. Signed-off-by:
-
Antti Palosaari authored
Now it supports IT9135 based dual tuner devices. Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
That same USB ID is used both AF9015 and AF9035 driver. iManufacturer is only thing we can select correct driver without a I/O. Signed-off-by:
-
Antti Palosaari authored
That same USB ID is used both AF9015 and AF9035 driver. iManufacturer is only thing we can select correct driver without a I/O. Signed-off-by:
-
Antti Palosaari authored
ADC needs to be also multiplied to 2 as it9135. Fixes bug I introduced few commits ago. Signed-off-by:
-
Antti Palosaari authored
Detect automatically multiple chip versions and select configuration according to that. Signed-off-by:
-
Antti Palosaari authored
Signed-off-by:
-
Antti Palosaari authored
Add support for tuners integrated to the IT9135 and IT9137. Signed-off-by:
-
Antti Palosaari authored
It is tuner driver for tuner integrated to the ITE IT9135 and IT9137 chips. I split it out from the current it913x-fe driver. Signed-off-by:
-
Kevin Baradon authored
My 15c2:0036 device floods syslog when a keypad key is pressed: Feb 18 19:00:57 homeserver kernel: imon 5-1:1.0: imon_incoming_packet: unknown keypress, code 0x100fff2 Feb 18 19:00:57 homeserver kernel: imon 5-1:1.0: imon_incoming_packet: unknown keypress, code 0x100fef2 Feb 18 19:00:57 homeserver kernel: imon 5-1:1.0: imon_incoming_packet: unknown keypress, code 0x100fff2 Feb 18 19:00:57 homeserver kernel: imon 5-1:1.0: imon_incoming_packet: unknown keypress, code 0x100fff2 Feb 18 19:00:57 homeserver kernel: imon 5-1:1.0: imon_incoming_packet: unknown keypress, code 0x100fff2 This patch removes those messages from imon, following suggestion from Mauro. Unknown keys shall be correctly handled by rc/input layer. Signed-off-by:
Kevin Baradon <kevin.baradon@gmail.com> Signed-off-by:
-
Kevin Baradon authored
Some imon devices (like 15c2:0036) need a higher delay between send_packet calls. Default value is still 5ms to avoid regressions on already working hardware. Also use interruptible wait to avoid load average going too high (and let caller handle signals). Signed-off-by:
-
Federico Fuga authored
If no manager is connected to the vout device, the omapvid_init() function fails. No error condition is checked, and the device is started. Later on, when irq is serviced, a NULL pointer dereference occurs. Also, the isr routine must be registered only if no error occurs, otherwise the isr triggers without the proper setup, and the kernel oops again. To prevent this, the error condition is checked, and the streamon function exits with error. Also the isr registration call is moved after the setup procedure is completed. Reviewed-by:
Prabhakar Lad <prabhakar.lad@ti.com> Signed-off-by:
-
