On Tue, Feb 17, 2009 at 01:42:19PM +0200, Mike Rapoport wrote: > The difficulty here is to find out when BTN_TOUCH should be generated and what > should be its value. As far as I can see from different drivers, there's no > one-to-one correspondence between ABS_PRESSURE and BTN_TOUCH. For instance, > drivers/input/mouse/synaptics.c has As a default it should be fine to check for zero/non-zero. Anything that wants to override the behaviour could supply their own BTN_TOUCH. Another option would be to change Android user space to support pressure only touchscreens. Like I say, I'm fine with the patch itself so it's got my ack - it just feels like it fixes the problem at the wrong level. From that PoV consider it to have Acked-by: Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> -- 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
