summaryrefslogtreecommitdiff
path: root/drivers/usb
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@redhat.com>2012-09-28 14:04:21 (GMT)
committerMauro Carvalho Chehab <mchehab@redhat.com>2012-10-07 12:43:01 (GMT)
commit78ef81f6ea9649fd09d1fafcfa0ad68763172c42 (patch)
tree7e7737736c2c7b08cc9aa682538b91d6cbda9538 /drivers/usb
parent034351ff6372c1a880ed4c5d333e430e9c83d467 (diff)
downloadlinux-fsl-qoriq-78ef81f6ea9649fd09d1fafcfa0ad68763172c42.tar.xz
[media] tda18271-common: hold the I2C adapter during write transfers
The tda18271 datasheet says: "The image rejection calibration and RF tracking filter calibration must be launched exactly as described in the flowchart, otherwise bad calibration or even blocking of the TDA18211HD can result making it impossible to communicate via the I2C-bus." (yeah, tda18271 refers there to tda18211 - likely a typo at their datasheets) That likely explains why sometimes tda18271 stops answering. That is now happening more often on designs with drx-k chips, as the firmware is now loaded asyncrousnly there. While the above text doesn't explicitly tell that the I2C bus couldn't be used by other devices during such initialization, that seems to be a requirement there. So, let's explicitly use the I2C lock there, avoiding I2C bus share during those critical moments. Compile-tested only. Please test. Acked-by: Michael Krufky <mkrufky@linuxtv.org> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'drivers/usb')
0 files changed, 0 insertions, 0 deletions