Hi Dmitry, Anatolij, On 15.11.2011 21:41, Dmitry Torokhov wrote: >>> Do you really need to read gpio state in IRQ? Can't you simply rely on >>> 'event' do decide whether to emit input events? >> >> We can't rely on the 'event' only. The peculiar behaviour of the >> touch controller enforces this. The touch controller toggles the >> interrupt line when you keep the finger down. The rate is not exactly >> specified by the the manufacturer (~80/sec). Measured rate deviates >> from this specified rate. Valid touch packet data can be read when >> interrupt line is pulled down. > > So what ensures that the gpio line stays low between the check and the > time you get access to i2c bus and get around reading the data. Anatolij, could you please comment on this? What can we do about this? Check the pin state after i2c read maybe? >> The designer of the target device >> insisted on driver implementation reading touch packet data only >> when irq line is pulled down. > > Well... have you tried checkign whether it is really necessary. Because > if it is not necessary you could do away with the platform data > altogether. My understanding is that it's really necessary. We had initial driver version without this checking and that resulted in some troubles. I'd like to drop the platform data too, but I think we really need it. Regards, Ilya. -- 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
