summaryrefslogtreecommitdiff
path: root/linux/drivers/media/dvb/dvb-usb/dtt200u.c
diff options
context:
space:
mode:
authorPatrick Boettcher <pb@linuxtv.org>2008-09-06 18:45:27 +0200
committerPatrick Boettcher <pb@linuxtv.org>2008-09-06 18:45:27 +0200
commite57c2bd89fdf14fd8cf07a300289c3af4b303594 (patch)
tree1d8dd99181961d990490ed895cd2980ece71a39d /linux/drivers/media/dvb/dvb-usb/dtt200u.c
parentf6b31c86cbf9e9833b40bded9ba5b31bf882fd2e (diff)
downloadmediapointer-dvb-s2-e57c2bd89fdf14fd8cf07a300289c3af4b303594.tar.gz
mediapointer-dvb-s2-e57c2bd89fdf14fd8cf07a300289c3af4b303594.tar.bz2
Add support for new i2c API provided in firmware version 1.20
From: Devin Heitmueller <devin.heitmueller@gmail.com> The Pinnacle PCTV HD Pro has an xc5000, which exposed a bug in the dib0700's i2c implementation where it did not properly support a single i2c read request (sending it as an i2c write request instead). Version 1.20 of the firmware added support for a new i2c API which supported such requests. This change defaults to fw 1.20 for all devices, but does not default to using the new i2c API (since initial testing suggests problems interacting with the mt2060). Maintainers can enable the use of the new i2c API by putting the following into their frontend initialization: struct dib0700_state *st = adap->dev->priv; st->fw_use_new_i2c_api = 1; Also note that the code expects i2c repeated start to be supported. If the i2c slave does not support repeated start, i2c messsages should have the I2C_M_NOSTART flag set. Thanks to Patrick Boettcher <patrick.boettcher@desy.de> for providing new firmware fixing the issue as well as example i2c code utilizing the interface. Priority: normal Signed-off-by: Devin Heitmueller <devin.heitmueller@gmail.com> Signed-off-by: Patrick Boettcher <pb@linuxtv.org>
Diffstat (limited to 'linux/drivers/media/dvb/dvb-usb/dtt200u.c')
0 files changed, 0 insertions, 0 deletions