Hello David, Sorry for the late response.
On 01/20/2016 04:41 PM, David Engel wrote:
Javier and Mauro, this is in regards to Debian bug #810726, which I filed last week. I also informed Hans about it at that time. Using git bisect, I finally identified the attached commit as the offending one. Sure enough, after reverting that change, my hdpvr behaves reliably with the 4.3.3 kernel. Further testing has revealed that I can achieve the same result with the standard, Debian kernel by blacklisting the ir_kbd_i2c module.
The attached commit is only fixing module autoloading for the I2C driver so is just exposing a existent bug. If you built the driver in the image instead of as a module, the bug should be present even with that commit reverted.
It seems something in the IR initialization is causing the hdpvr to become unreliable. This is even when the IR support is not used nor wanted. Additionally, blacklisting the lirc_zilog module is not sufficient to work around the problem, nor is keeping it but using the tx_only=1 parameter.
I believe the root cause has to be found since as I said, it was only working because the module didn't have the module alias information so udev/kmod were not able to load the module when the kernel report the MODALIAS uevent when the I2C device was registered.
David
Best regards, -- Javier Martinez Canillas Open Source Group Samsung Research America
