This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/TSC2013-Q1: a short and quick tap generates an interrupt, but retrieved status shows 0080 (Data not available)

Part Number: TSC2013-Q1

Tool/software: Linux

  Hi. I use TSC2013 chip and reference Linux driver (tsc2013.c, by Andy Liu) for building a product. When I make a solid tap on screen, interrupts are generated multiple times, and retrieved status register shows F080, which means that new xyz data is available. That is fine.  On the other hand, when a short and quick tap is made on screen, a couple of interrupt is generated, and retrieved status register shows 0080, which means data is not available.  Indeed, retrieved xyz data shows no changes from previous successful tap.

  My question is that why interrupt is generated if no data is ready yet,  and is there any register configurations that recognize x-y-z of a short and quick tap successfully?