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: Wed, 22 Jul 2026 10:41:09 +0000 [thread overview]
Message-ID: <bug-221774-208809-9J9sEBk790@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221774-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221774
Lovekesh Solanki (lovekeshsolanki00@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lovekeshsolanki00@gmail.com
--- Comment #2 from Lovekesh Solanki (lovekeshsolanki00@gmail.com) ---
It is possible the commit e716edafedad causes mt_get_feature() to reject the
Win8 response due to firmware returning mismatched report Id. So
hid_report_raw_event() is never reached and device doesn't switch into
Precision mode.
Rather than reverting the commit, which would drop the ID check for every
device, it may be possible to add a quirk for 0b05:1a30 so only this model
tolerates the mismatch.
I have prepared a patch which does that, but I don't have the hardware so I
cannot confirm.
Would it be possible for someone to test it? I'm not sure how to send it here
I'm not familiar with the process.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-07-22 10:41 UTC|newest]
Thread overview: 5+ 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 [this message]
2026-07-22 13:03 ` bugzilla-daemon
2026-07-22 15:07 ` 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-9J9sEBk790@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.