summaryrefslogtreecommitdiff
path: root/drivers/media/usb/em28xx/em28xx-reg.h
diff options
context:
space:
mode:
authorFrank Schaefer <fschaefer.oss@googlemail.com>2013-03-26 13:38:36 -0300
committerMauro Carvalho Chehab <mchehab@redhat.com>2013-03-28 17:37:45 -0300
commita3ea4bf98bc8499e64b619808fcca09ca3eb4e2f (patch)
tree0e4e41e215a6008bd6f0131a7dd90350223f9147 /drivers/media/usb/em28xx/em28xx-reg.h
parent80f23305ba43f9eda9596092735bffc283b9ae8d (diff)
downloadlinux-a3ea4bf98bc8499e64b619808fcca09ca3eb4e2f.tar.gz
linux-a3ea4bf98bc8499e64b619808fcca09ca3eb4e2f.tar.xz
[media] em28xx: add support for em25xx i2c bus B read/write/check device operations
The webcam "SpeedLink VAD Laplace" (em2765 + ov2640) uses a special algorithm for i2c communication with the sensor, which is connected to a second i2c bus. We don't know yet how to find out which devices support/use it. It's very likely used by all em25xx and em276x+ bridges. Tests with other em28xx chips (em2820, em2882/em2883) show, that this algorithm always succeeds there although no slave device is connected. The algorithm likely also works for real i2c client devices (OV2640 uses SCCB), because the Windows driver seems to use it for probing Samsung and Kodak sensors. Signed-off-by: Frank Schäfer <fschaefer.oss@googlemail.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'drivers/media/usb/em28xx/em28xx-reg.h')
0 files changed, 0 insertions, 0 deletions