linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cedric Sodhi <manday@gmx.net>
To: Chris Bagwell <chris@cnpbagwell.com>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
	linux-input@vger.kernel.org
Subject: Re: HID: Dead ./debug/hid/xxx/events
Date: Wed, 16 Nov 2011 15:55:18 +0100	[thread overview]
Message-ID: <20111116145518.GA7080@slate> (raw)
In-Reply-To: <CAGzDe_bdyvOnMJb12gQN9wPSn_dk-g_HxgkEP-x_3DRtB+gP1g@mail.gmail.com>

On Wed, Nov 16, 2011 at 07:41:04AM -0600, Chris Bagwell wrote:
> And a little extra info.  Cedric tested the patch that is now in
> Jiri's upstream-fixes branch for this new 0xa0001 and got success so I
> sent in patch.  After several days, he tested closer and realized it
> was getting X/Y movement and what I'll call unpredictable Touch
> behaviour.  It would either act like a stylus hovering but never
> touching or it would always act like touching and never release.
> 
> Events are working and you can test with evtest.  I've verified at
> least one test stream he emailed that it is not correctly sending
> BTN_TOUCH but it is sending good X/Y using MT and pointer emulation
> events.
> 
> It would probably be easy to see the issue if debug/hid/*/events were
> being displayed but for some reason "cat rdesc" outputs stuff but "cat
> events" does not.  I couldn't come up with more ideas remotely.
> 
> The redesc shows it reports ContactID's range of 0-16 and features
> says only 10 touches max (seen in above paste link).  So my last guess
> is that we may be using the wrong quirk for this one since it sounds
> like ContactID is not 1-to-1 with touches.  Hard to tell without
> sample events though.
> 
> Chris

Chris, it might interest you that the event node now fires and outputs
events, when letting hid-multitouch handle the device through Benjamin's
patch (Writing "3 0eef a001 1" to new_id).

I think when adding the MULTITOUCH5 in the source in the exact same
manner MULTITOUCH[1-4] are added I must have copied some quirks which
interfere with the event node. Now, adding the device by Benjamin's way
does not load any quirks by default, so the event node works.

Either Benjamin or I will tell you more once we discovered something
definite.

regards,
Cedric

  reply	other threads:[~2011-11-16 14:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16  9:50 HID: Dead ./debug/hid/xxx/events Cedric Sodhi
2011-11-16 10:17 ` Benjamin Tissoires
2011-11-16 10:25   ` Cedric Sodhi
2011-11-16 13:41     ` Chris Bagwell
2011-11-16 14:55       ` Cedric Sodhi [this message]
2011-11-16 15:40         ` Cedric Sodhi
2011-11-16 16:15           ` Chris Bagwell
2011-11-16 17:01             ` Benjamin Tissoires
2011-11-16 20:48               ` Cedric Sodhi
2011-11-16 21:22                 ` Benjamin Tissoires
2011-11-17  6:58                   ` Cedric Sodhi
2011-11-16 21:23                 ` Chris Bagwell
2011-11-17  6:59                   ` Cedric Sodhi

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=20111116145518.GA7080@slate \
    --to=manday@gmx.net \
    --cc=benjamin.tissoires@gmail.com \
    --cc=chris@cnpbagwell.com \
    --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).