linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Ping Cheng <pinglinux@gmail.com>
Cc: Chris Bagwell <chris@cnpbagwell.com>, linux-input@vger.kernel.org
Subject: Re: [PATCH 2/2]input - wacom_w8001: Add one finger touch support
Date: Thu, 9 Dec 2010 11:50:35 -0800	[thread overview]
Message-ID: <20101209195035.GD23781@core.coreip.homeip.net> (raw)
In-Reply-To: <AANLkTi=w3uOQKFN3WBgzib9M0Cb143vChPPaYm6fWypi@mail.gmail.com>

On Thu, Dec 09, 2010 at 11:36:19AM -0800, Ping Cheng wrote:
> On Thu, Dec 9, 2010 at 7:06 AM, Chris Bagwell <chris@cnpbagwell.com> wrote:
> > On Wed, Dec 8, 2010 at 7:23 PM, Ping Cheng <pinglinux@gmail.com> wrote:
> >> @@ -228,9 +277,17 @@ static irqreturn_t w8001_interrupt(struct serio *serio,
> >>                if (tmp == W8001_TOUCH_BYTE)
> >>                        break;
> >>
> >> +               if (w8001->has_touch) {
> >> +                       /* send touch data out */
> >> +                       w8001->has_touch = 0;
> >> +                       input_report_key(dev, BTN_TOUCH, 0);
> >> +                       input_report_key(dev, BTN_TOOL_FINGER, 0);
> >
> > Probably its better to set ABS_X/ABS_Y to zero and do a sync here?  So
> > duplicate x/y values don't get dropped and aligns with wacom_wac.c.
> > This is related to comment about forcing ABS_X/Y to zero above.  Its
> > so pen has known starting point when coming in proximity.  I wouldn't
> > do one without the other.
> 
> I'll do both to make you happy (just kidding, to make it safe ;).
> 

Actually do not see how (0,0) is any safer than let's say (123,78)
sincve i believe (0,0) is a valid coordinate. Userspace should still
hang on to the last reported coordinate and use it if it did not get
a new one.

Also, if you add input_sync() here won't it cause (in certain
situtations) false click or tap events - BTN_TOUCH goes from 1 to 0 and
then again to 1 if pen is already in proximity...

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-12-09 19:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09  1:23 [PATCH 2/2]input - wacom_w8001: Add one finger touch support Ping Cheng
2010-12-09  6:44 ` Dmitry Torokhov
2010-12-09 17:39   ` Ping Cheng
2010-12-09 18:02     ` Dmitry Torokhov
2010-12-09 15:06 ` Chris Bagwell
2010-12-09 19:36   ` Ping Cheng
2010-12-09 19:50     ` Dmitry Torokhov [this message]
2010-12-09 21:21       ` Chris Bagwell
2010-12-10  1:29         ` Ping Cheng
2010-12-10 13:39           ` Chris Bagwell
2010-12-10  7:38         ` Dmitry Torokhov
2010-12-10 13:47           ` Chris Bagwell
2010-12-10 17:37             ` Ping Cheng

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=20101209195035.GD23781@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=chris@cnpbagwell.com \
    --cc=linux-input@vger.kernel.org \
    --cc=pinglinux@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;
as well as URLs for NNTP newsgroup(s).