Re: [PATCH] [media] af9035: fix for MXL5007T devices with I2C read issues

2016-04-21 Thread Alex Rad
On Thu, Apr 21, 2016 at 2:12 AM, Antti Palosaari wrote: > On 04/20/2016 12:13 PM, Alex Rad wrote: >> >> On Wed, Apr 20, 2016 at 1:02 AM, Antti Palosaari wrote: >>> >>> Hello >>> I am not happy with that new module parameter as I cannot see real need >>> for >>> it. So

Re: [PATCH] [media] af9035: fix for MXL5007T devices with I2C read issues

2016-04-20 Thread Antti Palosaari
On 04/20/2016 12:13 PM, Alex Rad wrote: On Wed, Apr 20, 2016 at 1:02 AM, Antti Palosaari wrote: Hello I am not happy with that new module parameter as I cannot see real need for it. So get rid of it. My reasoning for this is: 1) We know of just two devices which may have the

Re: [PATCH] [media] af9035: fix for MXL5007T devices with I2C read issues

2016-04-20 Thread Alex Rad
On Wed, Apr 20, 2016 at 1:02 AM, Antti Palosaari wrote: > Hello > I am not happy with that new module parameter as I cannot see real need for > it. So get rid of it. My reasoning for this is: 1) We know of just two devices which may have the issue, but there are probably more. The

Re: [PATCH] [media] af9035: fix for MXL5007T devices with I2C read issues

2016-04-19 Thread Antti Palosaari
Hello I am not happy with that new module parameter as I cannot see real need for it. So get rid of it. Better to compare both VID and PID when enabling that work-around. Driver supports currently quite many different USB IDs and there is still small risk duplicate PID will exists at some

[PATCH] [media] af9035: fix for MXL5007T devices with I2C read issues

2016-04-15 Thread Alessandro Radicati
The MXL5007T tuner will lock-up on some devices after an I2C read transaction. This patch adds a kernel module parameter "no_read" to work around this issue by inhibiting such operations and emulating a 0x00 response. The workaround is applied automatically to USB product IDs known to exhibit