mirror of
https://github.com/torvalds/linux.git
synced 2024-11-07 12:41:55 +00:00
e530a5e3cf
Looking at the windows inf file, for usb ids with a sensor type where probing is needed to determine the type (for example ov7630 or soi768), this is needed for all bridge variants with a usb id indicating this sensor type. So do the probing to determine the actual sensor type for types where the usb-id info is not 100% deterministic, independent of the bridge type. If you look through the list of currently active usb ids in sonixj, this effectively only changes the code path for 0c45:60fe (sn9c105 + ov7630) and 0c45:612e (sn9c110 + ov7630), which according to the inf file can have a soi768 instead of a ov7630 just like the sn9c120 + ov7630 models where we already probe for a soi7630. The main reason for this code change is to keep the code paths as bridge variant independent as possible, so that we don't need a lot of special per bridge cases, as we enable more usb-ids in the future. This change makes the 0c45:60fe code path identical to the successfully tested 0c45:613e, so also make sonixj the default driver for 0c45:60fe. Signed-off-by: Hans de Goede <hdegoede@redhat.com> Acked-by: Jean-Francois Moine <moinejf@free.fr> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com> |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| sn9c102_config.h | ||
| sn9c102_core.c | ||
| sn9c102_devtable.h | ||
| sn9c102_hv7131d.c | ||
| sn9c102_hv7131r.c | ||
| sn9c102_mi0343.c | ||
| sn9c102_mi0360.c | ||
| sn9c102_mt9v111.c | ||
| sn9c102_ov7630.c | ||
| sn9c102_ov7660.c | ||
| sn9c102_pas106b.c | ||
| sn9c102_pas202bcb.c | ||
| sn9c102_sensor.h | ||
| sn9c102_tas5110c1b.c | ||
| sn9c102_tas5110d.c | ||
| sn9c102_tas5130d1b.c | ||
| sn9c102.h | ||