Dmitry Torokhov wrote: > On Mon, Jun 28, 2010 at 10:46:59AM +0200, Henrik Rydberg wrote: >> Dmitry Torokhov wrote: >>> On Mon, Jun 28, 2010 at 10:34:13AM +0200, Henrik Rydberg wrote: >>>> It is a bit confusing I agree, but the document is correct. The empty >>>> input_mt_sync() is used when there is no data to report, no lifted fingers, >>>> nothing. Just imagine a device which gets polled periodically. >>> If there is no new data to report why we need to call input_mt_sync() at >>> all? You can send input_sync() but input core will filter it out... >>> >> Yep, that is the reason. Admittedly, this is a corner cases that type A does not >> handle very gracefully, but it works. The only device so far where this seems >> useful is for the magic mouse, which does not want to report BTN_TOUCH at all. >> > > So what if we filter everything out? Userspace will never know that we > got an interrupt and will be just fine... > Userspace would still want to know if that last finger stayed on the pad the whole time, or if it was actually removed in between. Henrik -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
