All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Hans de Bruin <jmdebruin@xmsnet.nl>, linux-input@vger.kernel.org
Subject: Re: [PATCH] alps: Non interleaved V2 dualpoint has separate stick button bits
Date: Thu, 09 Apr 2015 14:49:10 +0200	[thread overview]
Message-ID: <55267546.6050408@redhat.com> (raw)
In-Reply-To: <20150408173815.GB14186@dtor-ws>

Hi,

On 08-04-15 19:38, Dmitry Torokhov wrote:
> On Wed, Apr 08, 2015 at 07:05:17PM +0200, Hans de Goede wrote:
>> Hi,
>>
>> On 08-04-15 18:24, Dmitry Torokhov wrote:
>>> On Wed, Apr 08, 2015 at 06:04:52PM +0200, Hans de Goede wrote:
>>>> Non interleaved V2 dualpoint touchpad / stick combos have separate stick
>>>> button bits in the touchpad packets, if we do not check these then the
>>>> trackpoint buttons will not work when using the touchpad, and when pressed
>>>> when the user starts using the touchpad will report a release event even
>>>> though the button is still pressed.
>>>>
>>>> This commit fixes this by checking the separate bits, note that we simply
>>>> combine the buttons, since the hardware does the same when using the touchpad
>>>> buttons with the trackpoint, so we do not have enough information to properly
>>>> separate them.
>>>
>>> Hmm, if they are designated as trackstick buttons why don't we report
>>> them as such (i.e. send button events out of dev2 without movement)?
>>
>> Because we may then end up with having a button pressed on both
>> the touchpad and trackstick evdev nodes, and if we then switch to
>> getting trackstick packets, which have one combined bit for both, and
>> the bit becomes 0 we end up releasing only one, which is what the commit
>> message tries to say with: "we do not have enough information to properly
>> separate them", I actually had an earlier version which did as you suggested,
>> but that become ugly pretty quickly.
>
> Oh, right... Do we get touchpad packets if both trackpoint and touchpad
> buttons are pressed and trackpoint is moved (bit no contacts on the pad)?

No, if the user does:

1) Press touchpad button
2) Move trackpoint

We get:

1) Touchpad packet with touchpad button pressed bit set
2) Trackpoint packets with "a button pressed" bit set and
movement

> Anyway, I guess it is older hardware and just mixing buttons is fine, no
> need to be super-fancy.

Ack, I'll do a v2 adding the requested documentation update tomorrow.

Regards,

Hans

  reply	other threads:[~2015-04-09 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 16:04 [PATCH] alps: Non interleaved V2 dualpoint has separate stick button bits Hans de Goede
2015-04-08 16:24 ` Dmitry Torokhov
2015-04-08 17:05   ` Hans de Goede
2015-04-08 17:38     ` Dmitry Torokhov
2015-04-09 12:49       ` Hans de Goede [this message]
2015-04-12 22:59         ` Dmitry Torokhov

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=55267546.6050408@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jmdebruin@xmsnet.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.