[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>
This commit is contained in:
parent
bde0368432
commit
52f1f2303f
1 changed files with 5 additions and 0 deletions
|
@ -301,6 +301,11 @@ int em28xx_detect_sensor(struct em28xx *dev)
|
||||||
if (dev->em28xx_sensor == EM28XX_NOSENSOR && ret < 0)
|
if (dev->em28xx_sensor == EM28XX_NOSENSOR && ret < 0)
|
||||||
ret = em28xx_probe_sensor_omnivision(dev);
|
ret = em28xx_probe_sensor_omnivision(dev);
|
||||||
|
|
||||||
|
/*
|
||||||
|
* NOTE: the Windows driver also probes i2c addresses
|
||||||
|
* 0x22 (Samsung ?) and 0x66 (Kodak ?)
|
||||||
|
*/
|
||||||
|
|
||||||
if (dev->em28xx_sensor == EM28XX_NOSENSOR && ret < 0) {
|
if (dev->em28xx_sensor == EM28XX_NOSENSOR && ret < 0) {
|
||||||
em28xx_info("No sensor detected\n");
|
em28xx_info("No sensor detected\n");
|
||||||
return -ENODEV;
|
return -ENODEV;
|
||||||
|
|
Loading…
Reference in a new issue