aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/media/usb
diff options
context:
space:
mode:
authorFrank Schaefer <fschaefer.oss@googlemail.com>2013-03-27 16:06:35 -0400
committerMauro Carvalho Chehab <mchehab@redhat.com>2013-03-29 05:40:47 -0400
commit52f1f2303f131d6d287a5316e35a4ec0d8ac8b98 (patch)
tree69634061242b8b57e2b403598eba628f9b78d163 /drivers/media/usb
parentbde03684323d12b5da0834475bf9964f064a403b (diff)
[media] em28xx: add comment about Samsung and Kodak sensor probing addresses
The Windows driver also probes at least two further i2c addresses (0x22 >> 1 and 0x66 >> 1). I've got some hints that they are very likely used by Samsung and Kodak sensors, which are known to be used in Empia devices, too. We havn't seen any devices using these sensors yet and don't know how to probe them properly, so leave a comment. 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')
-rw-r--r--drivers/media/usb/em28xx/em28xx-camera.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/drivers/media/usb/em28xx/em28xx-camera.c b/drivers/media/usb/em28xx/em28xx-camera.c
index e8b3322242c0..64b70d42da1e 100644
--- a/drivers/media/usb/em28xx/em28xx-camera.c
+++ b/drivers/media/usb/em28xx/em28xx-camera.c
@@ -301,6 +301,11 @@ int em28xx_detect_sensor(struct em28xx *dev)
301 if (dev->em28xx_sensor == EM28XX_NOSENSOR && ret < 0) 301 if (dev->em28xx_sensor == EM28XX_NOSENSOR && ret < 0)
302 ret = em28xx_probe_sensor_omnivision(dev); 302 ret = em28xx_probe_sensor_omnivision(dev);
303 303
304 /*
305 * NOTE: the Windows driver also probes i2c addresses
306 * 0x22 (Samsung ?) and 0x66 (Kodak ?)
307 */
308
304 if (dev->em28xx_sensor == EM28XX_NOSENSOR && ret < 0) { 309 if (dev->em28xx_sensor == EM28XX_NOSENSOR && ret < 0) {
305 em28xx_info("No sensor detected\n"); 310 em28xx_info("No sensor detected\n");
306 return -ENODEV; 311 return -ENODEV;