From: Dmitry Torokhov <dtor_core@ameritech.net>
To: "Shaun Jackman" <sjackman@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] elo: Support non-pressure-sensitive ELO touchscreens
Date: Tue, 28 Mar 2006 01:10:46 -0500 [thread overview]
Message-ID: <200603280110.47199.dtor_core@ameritech.net> (raw)
In-Reply-To: <7f45d9390603271515m17a5ee1due5bc3f9f2285ca62@mail.gmail.com>
On Monday 27 March 2006 18:15, Shaun Jackman wrote:
> On 3/27/06, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > We should not only omit reporting pressure if toucscreen does not
> > support it but also not set ABS_PRESSURE bit in input device.
>
> Can I simply call input_set_abs_params and serio_set_drvdata again to
> change these bits on the fly based on the 'T' packets? What value
> should be the default before a 'T' packet has been received? I'd
> suggest no pressure.
>
No, we should not change basic input device's capabilities "on-fly" -
userspace should be able to rely on what was reported to it in the first
place. From looking over the documentation (thank you for the link)
it looks like you would need to issue 'i' command to query controller
type and whether the controller supports Z-axis in elo_connect().
> > What is the reason for postponing checking for 'T' until full packet
> > is assembled? Did you actually see packets with valid checksum but
> > without 'T'?
>
> I believe the 'T' packet is the only packet that the touchscreen sends
> unrequested. However, the touch screen can send a number of other
> packets as well. The protocol documentation is available from Elo:
>
> http://elotouch.com/files/manuals/smartset.zip
>
OK, I see.
--
Dmitry
next prev parent reply other threads:[~2006-03-28 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7f45d9390602241045p45aec8auaf881a4dab00c17a@mail.gmail.com>
[not found] ` <7f45d9390603151047t7f18b3afn4fcf899ff8368aa3@mail.gmail.com>
2006-03-27 16:28 ` [PATCH] elo: Support non-pressure-sensitive ELO touchscreens Dmitry Torokhov
[not found] ` <7f45d9390603271515m17a5ee1due5bc3f9f2285ca62@mail.gmail.com>
2006-03-28 6:10 ` Dmitry Torokhov [this message]
[not found] ` <7f45d9390603280709u5eea134ejb0aaacdd49984a92@mail.gmail.com>
2006-07-19 21:34 ` Shaun Jackman
2006-07-21 6:10 ` Dmitry Torokhov
2006-07-21 20:25 ` Shaun Jackman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200603280110.47199.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sjackman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox