Re: [PATCH] new driver for ITM Touch touchscreen

From: Dmitry Torokhov (dmitry.torokhov_at_gmail.com)
Date: 03/04/05

  • Next message: Rusty Russell: "Re: Undefined symbols in 2.6.11-rc5-mm1" 
    Date:	Fri, 4 Mar 2005 11:54:18 -0500
To: Hans-Christian Egtvedt <hc@mivu.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!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: Rusty Russell: "Re: Undefined symbols in 2.6.11-rc5-mm1"

    Relevant Pages

    • Re: [PATCH] new driver for ITM Touch touchscreen
      ... I think you need to use some threshold when reporting BTN_TOUCH ... > driver adjust touchpad sensitivity, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.13-rc5 randconfig kernel build errors
      ... I'll settle:) It is this feedback I need at ... without reporting stuff to the list. ... I looked at that AmlCode error source file and grepping for a match ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [oom]: [0/4] fix OOM deadlock running OAST
      ... The vast majority of all this are the couhters for reporting, ... The actual functional effect is achieved by ... pagecache from the LRU lists, which is performance, not correctness. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] Light-weight Auditing Framework
      ... > 2) added syscall exit status reporting and testing ... > * will only be written if another part of the kernel requests that it ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Tracing memory leaks (slabs) in 2.6.9+ kernels?
      ... Will the slab debugger make it into the kernel as a standard compile ... >> address reporting. ... > +#if DEBUG ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)