On Sun, 06 May 2012 20:17:08 +0200 Hans de Goede <hdegoede@xxxxxxxxxx> wrote: > > - as it is (read the register 11 every 100 ms), the work queue is > > usefull when there is no polling of the snapshot button, because the > > frame overflow is reported as the bit 0 in the forth byte (data[3]) > > of the interrupt messages. > > Interesting, so if the interrupt is enabled, then as soon as an overflow > happens, we get notified through the interrupt data? > > That may be an alternative to the worker thread, although the current > solution does work rather well, so I wonder if we should meddle with it. Hi Hans, Indeed, your solution works, but it does double polling, and the actual worker thread asks for a USB exchange each 100 ms. When using only the interrupt message, there is no overhead. Regards. -- 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
