On Fri, Apr 25, 2008 at 08:47:23PM +0200, Sebastian Siewior wrote: > * Dmitry Torokhov | 2008-04-25 14:32:53 [-0400]: > > >> >Plus, you might want > >> >to select some kind of pressure thresholds before reporting touch press > >> >and release. > >> Sure but depending on what? Are there any drivers doing this allready? > >> I didn't find any on my grep. > >> Since these values are HW specifc they should be some userspace control > >> (like for max/min x/y). > > > >Synaptics for example does it. You just need to guesstimate what > >values are most likely to work by default (since you are trying to > >provide compatibility with a legacy interface, just to get user going) > >and then leave fine-tuning to evdev/tslib. > > The code: > | /* Post events > | * BTN_TOUCH has to be first as mousedev relies on it when doing > | * absolute -> relative conversion > | */ > | if (hw.z > 30) input_report_key(dev, BTN_TOUCH, 1); > | if (hw.z < 25) input_report_key(dev, BTN_TOUCH, 0); > > Nothing happens if z is lets say 27. Right, you want to have hysteresis to avoid jitter. > How do I do fine tunning with > evdev? This looks like nothing has any influence on 30 & 25. Synaptics native driver ignores BTN_TOUCH and goes strictly by ABS_PRESSURE. The same would be valid for evdev/tslib combo on UCB1400. BTN_TOUCH is for mousedev (and similar dumb consumers) benefit only. > My minimum pressure seems to be around 500 and I didn't get it past 700. > I get nothing if I touch lightly the touchscreen so I thing having > nothing is allready sane. Ah, OK then. -- Dmitry -- 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
