diff options
| author | Jean Delvare <khali@linux-fr.org> | 2010-05-26 10:05:11 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2010-06-01 01:23:19 -0300 |
| commit | 806b07c29b711aaf90c81d2a19711607769f8246 (patch) | |
| tree | ac9a5066c43dd086832a399af6e098efa28ffd5d /Documentation/bad_memory.txt | |
| parent | f137f9d0009067289a2fa6c4da9b82084cdd257e (diff) | |
| download | blackbird-op-linux-806b07c29b711aaf90c81d2a19711607769f8246.tar.gz blackbird-op-linux-806b07c29b711aaf90c81d2a19711607769f8246.zip | |
V4L/DVB: FusionHDTV: Use quick reads for I2C IR device probing
IR support on FusionHDTV cards is broken since kernel 2.6.31. One side
effect of the switch to the standard binding model for IR I2C devices
was to let i2c-core do the probing instead of the ir-kbd-i2c driver.
There is a slight difference between the two probe methods: i2c-core
uses 0-byte writes, while the ir-kbd-i2c was using 0-byte reads. As
some IR I2C devices only support reads, the new probe method fails to
detect them.
For now, revert to letting the driver do the probe, using 0-byte
reads. In the future, i2c-core will be extended to let callers of
i2c_new_probed_device() provide a custom probing function.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Tested-by: "Timothy D. Lenz" <tlenz@vorgon.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'Documentation/bad_memory.txt')
0 files changed, 0 insertions, 0 deletions
