linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chase Douglas <chasedouglas@gmail.com>
To: Thorsten Wissmann <re06huxa@stud.informatik.uni-erlangen.de>
Cc: "Chris Bagwell" <chris@cnpbagwell.com>,
	"Henrik Rydberg" <rydberg@euromail.se>,
	linux-input@vger.kernel.org,
	"Maximilian Krüger" <maxfragg@gmail.com>,
	i4passt@lists.informatik.uni-erlangen.de
Subject: Re: Mixed "pen" and multitouch input devices
Date: Thu, 15 Mar 2012 19:03:12 -0700	[thread overview]
Message-ID: <4F629F60.7010600@gmail.com> (raw)
In-Reply-To: <20120316015224.GA8230@stud.informatik.uni-erlangen.de>

On 03/15/2012 06:52 PM, Thorsten Wissmann wrote:
> On Thu, Mar 15, 2012 at 11:29:37AM -0700, Chase Douglas wrote:
>> On 03/15/2012 10:56 AM, Thorsten Wissmann wrote:
>>> On Thu, Mar 15, 2012 at 12:27:22PM -0500, Chris Bagwell wrote:
>>>> If you want to work with other unmodified user land apps (perhaps
>>>> xf86-input-evdev for touches) then its probably easiest to split pen
>>>> and touch to separate input devices.  drivers/input/tablet/wacom_wac.c
>>>> shows some examples of that approach but that driver doesn't have to
>>>> work to hard to split in to 2 input devices because the USB device
>>>> already puts the events on separate USB  interfaces.
>>>
>>> OK. We want the device to work with the xf86-input-evdev driver. So we
>>> will split it into two devices.
>>
>> Or you could teach evdev to know how to handle mixed devices :). I think
>> that's the "better" approach over all, but it's up to you.
> 
> Thanks! We didn't thought about this. It turned out that the problem
> isn't caused by the usage of both BTN_TOOL_PEN and BTN_TOOL_FINGER.
> 
> It turned out xf86-input-evdev really discards all non-multitouch events
> (especially ABS_X and ABS_Y) events in EvdevProcessAbsoluteMotionEvent()
> in evdev.c, if the device is configured as a multitouch device. So there
> is a quick fix (or only workaround?), which processes ABS_X and ABS_Y
> events even if it is a multitouch device:
> 
> diff --git a/src/evdev.c b/src/evdev.c
> index d540b87..b857b83 100644
> --- a/src/evdev.c
> +++ b/src/evdev.c
> @@ -832,7 +832,7 @@ EvdevProcessAbsoluteMotionEvent(InputInfoPtr pInfo,
> struct input_event *ev)
>      if (ev->code >= ABS_MT_SLOT) {
>          EvdevProcessTouchEvent(pInfo, ev);
>          pEvdev->abs_queued = 1;
> -    } else if (!pEvdev->mt_mask) {
> +    } else if (!pEvdev->mt_mask || ev->code == ABS_X || ev->code ==
> ABS_Y) {
>          map = pEvdev->axis_map[ev->code];
>          valuator_mask_set(pEvdev->vals, map, value);
>          pEvdev->abs_queued = 1;
> 
> This patch already is submitted to the xorg bugtracker and can be found
> at [1].
> 
> The only remaining question is: Does it break other drivers?
> 
>     Max and Thorsten
> 
> [1] https://bugs.freedesktop.org/show_bug.cgi?id=47382

Great!

I haven't fully thought about it enough to give a reviewed-by, but it
seems sane.

I suggest sending the patch to xorg-devel@lists.x.org. That's where most
patch reviews are handled. You will likely get faster results there.

-- Chase

  reply	other threads:[~2012-03-16  2:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 15:52 Mixed "pen" and multitouch input devices Thorsten Wissmann
2012-03-15 17:27 ` Chris Bagwell
2012-03-15 17:56   ` Thorsten Wissmann
2012-03-15 18:29     ` Chase Douglas
2012-03-16  1:52       ` Thorsten Wissmann
2012-03-16  2:03         ` Chase Douglas [this message]
2012-03-16  2:44           ` Thorsten Wissmann
2012-03-16  2:57           ` Chris Bagwell
2012-03-16 17:33             ` Thorsten Wissmann
2012-03-16 20:27               ` Chase Douglas
2012-03-19  6:39                 ` Henrik Rydberg
2012-03-19 15:32                   ` Chase Douglas
2012-03-20  1:04                     ` Chris Bagwell

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=4F629F60.7010600@gmail.com \
    --to=chasedouglas@gmail.com \
    --cc=chris@cnpbagwell.com \
    --cc=i4passt@lists.informatik.uni-erlangen.de \
    --cc=linux-input@vger.kernel.org \
    --cc=maxfragg@gmail.com \
    --cc=re06huxa@stud.informatik.uni-erlangen.de \
    --cc=rydberg@euromail.se \
    /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).