linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: linux-input@vger.kernel.org
Subject: Re: ABS_PRESSURE and 0 ranges
Date: Thu, 25 Oct 2012 11:34:54 -0700	[thread overview]
Message-ID: <20121025183452.GC24594@core.coreip.homeip.net> (raw)
In-Reply-To: <2119530.D54ZbrWB3u@devpool02>

Hi Rolf,

On Thu, Oct 25, 2012 at 02:59:49PM +0200, Rolf Eike Beer wrote:
> Hi all,
> 
> as I found out the hard way tslib does the detection if a touchscreen has been 
> "clicked" if the kernel driver says it does not support ABS_PRESSURE. But when 
> the kernel says it can do ABS_PRESSURE tslib will not do it's emulation and 
> just pass on whatever pressure value the kernel sends.
> 
> So far, so good. Sadly there are some drivers that do:
> 
> input_set_abs_params(dev, ABS_PRESSURE, 0, 0, 0, 0);
> 

What drivers are doing this?

> Guess what happens: no clicks at all. The question I have is: does the above 
> line make any sense to be in a kernel driver at all? Or is that some voodoo 
> that must be there and it's all tslib fault?
> 
> Now that I know where the problem is coming from the problem is easily 
> fixable, I'm just wondering which patch to make.

Well, the limits are strictly advisory for userspace, input core does
not perform any clamping or discarding the data that falls outside the
limits, so tslib probably should not do that either.

Thanks.

-- 
Dmitry

  reply	other threads:[~2012-10-25 18:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25 12:59 ABS_PRESSURE and 0 ranges Rolf Eike Beer
2012-10-25 18:34 ` Dmitry Torokhov [this message]
2012-10-25 20:11   ` Rolf Eike Beer
2012-10-25 20:51     ` Dmitry Torokhov
2012-10-25 21:45       ` Rolf Eike Beer

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=20121025183452.GC24594@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=eike-kernel@sf-tec.de \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).