Re: How should Touchscreen Input Drives behave (OpenEZX pcap_ts)

From: Harald Welte
Date: Thu May 18 2006 - 06:58:11 EST

Hi Richard,

thanks for your prompt reply.

On Thu, May 18, 2006 at 10:52:27AM +0100, Richard Purdie wrote:
> Hi,
> On Thu, 2006-05-18 at 09:07 +0200, Harald Welte wrote:
> > 0) What kind of X/Y/Pressure values should I return? Are they supposed
> > to be scaled to the X/Y resolution of the LCD? As of now, I return
> > X_ABS, Y_ABS and PRESSURE values between 0 and 1000 (each).
> >
> > However, the coordinates are actually inverted, so '0,0' corresponds
> > to the lower right corner of the screen, whereas '1000,1000' is the
> > upper left corner. Shall I invert them (i.e. return 1000-coord')?
> Just send the raw data to userspace. Any translations needed can be
> handled in userspace by the calibration program. You probably want to
> have a look at tslib:

ok, I'll investigate. Thanks for the hint.

> The range of the values also doesn't really matter and scaling would
> again get handled in userspace.


> Calibration happens in userspace and tslib stores the result
> in /etc/pointercal. If you device has this data stored in hardware, you
> could have a userspace app translate that data into such a file,
> otherwise, you can run a calibration program such as ts_calibrate (from
> tslib) or something like xtscal.

well, I guess re-calibrating using ts_calibrate will be easier than
trying to understand the proprietary calibration data format.

> If the user is pressing the screen at all, its a button event and
> release is when they stop touching the screen. I'd try not to make it
> depend upon pressure but it will depend on the hardware to a degree.

ok. I have observed that this specific hardware sometimes indicates a
pressure of '1' (out of a rage ~ 0...1000) even if the screen is not
pressed. So I think there should be some level (maybe 10/20), only
after this level of pressure has been reached it should report a button

> Admittedly, tslib doesn't do much with pressure information at the
> moment but tslib would the the correct place to handle pressure rather
> than have every kernel touchscreen driver doing it.

ok, i see. perfectly makes sense.

> For debugging, I'd highly recommend the test tools in tslib (ts_print,
> ts_calibrate and ts_test). Use them in that order, checking for sane
> output with ts_print first, get a working calibration second and finally
> prove its working with ts_test. I found them to be very useful when
> developing corgi_ts.

thanks again, will do so later today.

> I'm told you're thinking about using OpenEmbedded and would highly
> recommend it. It should easily be able to provide a known working
> userspace with tslib and these tools in.

yes, I've actually managed to do a full task-bootstrap and task-gpe for
the device now (cross-compiled from my linuxppc64 quad-g5), and was
quite amazed that it almost worked out of the box.

- Harald Welte <laforge@xxxxxxxxxxxx>
We all know Linux is does infinite loops in 5 seconds. -- Linus

Attachment: pgp00000.pgp
Description: PGP signature