public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Hans-Christian Egtvedt <hc@mivu.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] new driver for ITM Touch touchscreen
Date: Fri, 4 Mar 2005 11:54:18 -0500	[thread overview]
Message-ID: <d120d50005030408544462c9ea@mail.gmail.com> (raw)
In-Reply-To: <1109953224.3069.39.camel@charlie.itk.ntnu.no>

On Fri, 04 Mar 2005 17:20:24 +0100, Hans-Christian Egtvedt <hc@mivu.no> wrote:
> On Fri, 2005-03-04 at 09:52 -0500, Dmitry Torokhov wrote:
> > On Fri, 4 Mar 2005 14:03:37 +0200, Alexey Dobriyan <adobriyan@mail.ru> wrote:
> > > On Friday 04 March 2005 12:30, Hans-Christian Egtvedt wrote:
> 
> <snip info about kref>
> 
> > As far as the driver goes:
> >
> > - yes, it does need input_sync;
> 
> One problem with input_sync is that the panel get's too fast, and double
> click is experienced quite often, maybe some threshold is needed for low
> values in Z-direction?
> 
> I'm probably doing something wrong here since I experience easy
> doubleclicks when I just lightly touch the screen.
>

Yes, I think you need to use some threshold when reporting BTN_TOUCH
event. Still, always report ABS_PRESSURE as is. This way the
touchscreen is useable via legacy interfaces (mousedev. tsdev) and if
a specialized userspace driver is written it still can get pretty much
unmangled data from /dev/input/eventX. This will also allow such
driver adjust touchpad sensitivity, if needed.

> > Also, is there a way to query the screen for actual size?
> 
> Sorry, the panel is a fixed size, and it gives out coordinates from 0 ->
> 4095 in both X- and Y-direction. In Z-direction (pressure strength) it
> goes from 0 to 255.
> 
> Or did you want the size of the screen? Meaning you want to know if it's
> a 15", 17" and so on?
> 

No, not physical sizes. I was wondering if soe touchscreens are
reporting let's say actual coordinates from 1100-3600 and others from
600-3850, instead of full 0-4096. Is there a way to query the hardware
and find the actual min and max for a device so it can be reported to
userspace.

-- 
Dmitry

P.S. When you post the updated version could you please CC Vojtech
Pavlik <vojtech@suse.cz> as he is the current input system maintainer
and linux-input mailing list at linux-input@atrey.karlin.mff.cuni.cz.
Thanks!

  reply	other threads:[~2005-03-04 17:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 10:30 [PATCH] new driver for ITM Touch touchscreen Hans-Christian Egtvedt
2005-03-04 12:03 ` Alexey Dobriyan
2005-03-04 14:52   ` Dmitry Torokhov
2005-03-04 16:20     ` Hans-Christian Egtvedt
2005-03-04 16:54       ` Dmitry Torokhov [this message]
2005-03-04 18:51         ` Hans-Christian Egtvedt
2005-03-04 20:38           ` Vojtech Pavlik
2005-03-04 20:35         ` Vojtech Pavlik
2005-03-08 16:01         ` Hans-Christian Egtvedt
2005-03-08 17:25           ` Dmitry Torokhov
2005-03-08 17:49             ` Vojtech Pavlik
2005-03-08 18:23           ` Paulo Marques
2005-03-10 16:18           ` Vojtech Pavlik
2005-03-10 16:41             ` Hans-Christian Egtvedt
2005-03-10 16:46               ` Vojtech Pavlik

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=d120d50005030408544462c9ea@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=dtor_core@ameritech.net \
    --cc=hc@mivu.no \
    --cc=linux-kernel@vger.kernel.org \
    /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