mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: timon <timon37@lavabit.com>
To: "Thành Nguyễn" <thanhnguyxn07@gmail.com>, nikita@trvn.ru
Cc: linusw@kernel.org, dmitry.torokhov@gmail.com,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	linus.walleij@linaro.org
Subject: Re: [PATCH] Input: zinitix: iterate contact slots by finger count
Date: Tue, 14 Jul 2026 17:35:49 +0200	[thread overview]
Message-ID: <f0ceebbd-cf79-42d7-a32e-d7f92272ce1d@lavabit.com> (raw)
In-Reply-To: <CAPWvNi7ATfEKCC6qn+DTHnSLJxXamYiiNWA+1JgQmw2RG+PH6g@mail.gmail.com>

Sorry for not replying earlier (life), but I don't think the v2 patch 
will fully work correctly.

At least on my samsung a3 the loop needs to work as it did before 
e941dc13fd37.

Meaning: iterate over all slots and check the (sub_status & 
SUB_BIT_EXIST) for whether the finger is active or not.
Because: the active fingers can be in later slots with the earlier slots 
being inactive.

For example when the user:
1. touches with one finger (1 finger active in slot 0)
2. touches somewhere else with a second finger (2 fingers active in 
slots 0, 1)
3. lets go with the first finger (1 finger active in slot 1)

In such a case the loop would only iterate over slot 0 and not report 
any fingers despite slot 1 still being active.
In practice this will likely be usable... but afaik and can tell it's 
still incorrect behaviour.

Best Regards,
Timon

On 7/5/26 13:17, Thành Nguyễn wrote:
> Hi Nikita, Linus, and Dmitry,
>
> Thank you all for the feedback and for confirming the fix on your end, Nikita.
>
> Unfortunately, since it's been a while since I submitted the v2 patch,
> I recently had to completely wipe my development machine and no longer
> have the local environment or the original patch files to create a v3.
>
> Since the logic in v2 is sound and the only change needed is a brief
> comment explaining the dual mask/count nature of `finger_mask`, would
> one of you be willing to add that comment and apply the patch on my
> behalf? I'd really appreciate it.
>
> Thanks again for your time and help with getting this merged!
>
> Best regards,
> Thanh Nguyen



      reply	other threads:[~2026-07-14 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08  5:19 Thanh Nguyen
2026-06-30  9:11 ` Linus Walleij
2026-07-05  7:13   ` Nikita Travkin
2026-07-05 11:17     ` Thành Nguyễn
2026-07-14 15:35       ` timon [this message]

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=f0ceebbd-cf79-42d7-a32e-d7f92272ce1d@lavabit.com \
    --to=timon37@lavabit.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linusw@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikita@trvn.ru \
    --cc=thanhnguyxn07@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

Powered by JetHome