All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221774] hid-multitouch: report ID mismatch check breaks touchpad palm detection on ASUS ROG Flow Z13 (2025) GZ302EA (0b05:1a30)
Date: Fri, 24 Jul 2026 17:59:28 +0000	[thread overview]
Message-ID: <bug-221774-208809-mdPDDGxbXB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221774-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=221774

--- Comment #8 from Lovekesh Solanki (lovekeshsolanki00@gmail.com) ---
Okay it looks like the core fix works at least.

I think ABS_MT_TOOL_TYPE is missing because mt_touch_input_mapping() has a name
check for the MT_CLS_WIN_8* classes which enables the MT_QUIRK_CONFIDENCE quirk
which is later checked for to enable ABS_MT_TOOL_TYPE. And since the device now
has its own class it does not pass the check.
Adding MT_QUIRK_CONFIDENCE explicitly should recover the missing
ABS_MT_TOOL_TYPE.

I'm attaching an updated patch, could you run the same tests you ran before?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-07-24 17:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  2:37 [Bug 221774] New: hid-multitouch: report ID mismatch check breaks touchpad palm detection on ASUS ROG Flow Z13 (2025) GZ302EA (0b05:1a30) bugzilla-daemon
2026-07-22  6:42 ` [Bug 221774] " bugzilla-daemon
2026-07-22 10:41 ` bugzilla-daemon
2026-07-22 13:03 ` bugzilla-daemon
2026-07-22 15:07 ` bugzilla-daemon
2026-07-23 18:24 ` bugzilla-daemon
2026-07-24  9:28 ` bugzilla-daemon
2026-07-24 13:14 ` bugzilla-daemon
2026-07-24 17:59 ` bugzilla-daemon [this message]
2026-07-24 18:00 ` bugzilla-daemon

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=bug-221774-208809-mdPDDGxbXB@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@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.