public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221318] mice behind ASMedia ASM1042A via Thunderbolt 2 never produce input, most likely due to interrupt pipe idle window during enumeration
Date: Sat, 04 Apr 2026 09:54:27 +0000	[thread overview]
Message-ID: <bug-221318-208809-HWxfBGqGQ4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221318-208809@https.bugzilla.kernel.org/>

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

Michał Pecio (michal.pecio@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michal.pecio@gmail.com

--- Comment #1 from Michał Pecio (michal.pecio@gmail.com) ---
ASM1042A is a host controller, not a hub, but there is likely a hub between
ASM1042A and the USB ports on the monitor. Maybe the same hub which shows up
when the monitor is plugged into USB instead of Thunderbolt.

Could you post "lsusb -tv" for both connection variants with the same mouse in
the same monitor port?

Maybe see if dynamic debug spits out something useful:

echo 'module xhci_hcd +p' >/proc/dynamic_debug/control
dmesg -W >log.txt

Then connect the mouse with your udev rule, make a few clicks, disconnect,
remove the udev rule, connect again, make a few clicks. Attach the resulting
log.

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

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

  reply	other threads:[~2026-04-04  9:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03 20:22 [Bug 221318] New: mice behind ASMedia ASM1042A via Thunderbolt 2 never produce input, most likely due to interrupt pipe idle window during enumeration bugzilla-daemon
2026-04-04  9:54 ` bugzilla-daemon [this message]
2026-04-04 17:32 ` [Bug 221318] " bugzilla-daemon
2026-04-04 17:33 ` bugzilla-daemon
2026-04-04 17:34 ` bugzilla-daemon
2026-04-04 17:35 ` bugzilla-daemon
2026-04-04 17:39 ` bugzilla-daemon
2026-04-04 21:02 ` bugzilla-daemon
2026-04-05 22:09 ` bugzilla-daemon
2026-04-05 22:37 ` bugzilla-daemon
2026-04-05 22:44 ` bugzilla-daemon
2026-04-06  8:30 ` bugzilla-daemon
2026-04-06 11:35 ` bugzilla-daemon
2026-04-06 11:36 ` bugzilla-daemon
2026-04-06 11:54 ` bugzilla-daemon
2026-04-06 15:35 ` bugzilla-daemon
2026-04-06 19:56 ` bugzilla-daemon
2026-04-06 20:06 ` bugzilla-daemon
2026-04-06 20:11 ` bugzilla-daemon
2026-04-07  7:13 ` bugzilla-daemon
2026-04-07 13:18 ` bugzilla-daemon
2026-04-09 22:29 ` 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-221318-208809-HWxfBGqGQ4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox