rydberg@xxxxxxxxxxx wrote: > On Thu, Jun 27, 2013 at 01:49:20PM +0100, Nick Dyer wrote: >> If fingers are down as the MXT chip goes into suspend it does not send a lift >> message. In addition, it may not complete its final measurement cycle >> immediately, which means touch messages may be received by the interrupt >> handler after mxt_stop() has completed. > > How long is the window of possible stray interrupts? Could this be > done with a small delay instead of keeping track of the suspend state? The touch controller has its own acquisition scheduling which switches between active/idle modes. Which mode it is in isn't explicitly communicated to the driver. If we could tell it was in active mode (which would involve some hairier code than this patch involves), we might have to wait ~20ms on a modern device. But the worst case is that we would have to wait for the idle scan interval plus some margin, so a couple of hundred ms. I think that is too long, right? -- 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
