Hello, light source is not related to LEDs, it is for the kind of light source (tungsten, etc). The Windows driver had this control beside the white balance. I could remove this new control as under Windows the white balance is achieved by software and not hardware so the white balance control is available with Linux. About delay, they are required with at least 2 of four sensors managed by the driver because there can be communication faults. It also depends on the laptop as a same sensor driver is kown to always fails with a laptop and not another one. I prefer now to secure the communication with all four sensors with a small delay after a data has been sent. The delay is mostly stringent in the case of the MI2020 because there is more than 400 USB messages sent to the webcam at startup and initialisation time. Added with other required delay, several seconds are needed to initialise the webcam. I know a "msleep(1)" lasts 5ms to 10ms depending on the scheduler. The msleep slows down too much the communication. The OV2640 requires also more than 200 messages. I never got any error with 850ms but we could use 900 or 1000ms. I chose the less long delay. Cheers, OL 2010/3/1, Jean-Francois Moine <moinejf@xxxxxxx>: > On Sun, 28 Feb 2010 21:19:25 +0100 > Olivier Lorin <olorin75@xxxxxxxxx> wrote: > >> - General changes for all drivers because of new MI2020 sensor >> driver : >> - add the light source control >> - control value changes only applied after an end of image >> - replace msleep with duration less than 5 ms by a busy loop >> - Fix for an irrelevant OV9655 image resolution identifier name > > Hello Olivier, > > What is this 'light source'? In the list, we are talking about the > webcam LEDs and how to switch them on/off. Is it the same feature? > > Is it important to have a so precise delay in the webcam exchanges? > > Cheers. > > -- > Ken ar c'hentañ | ** Breizh ha Linux atav! ** > Jef | http://moinejf.free.fr/ > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
