From: Michal Pecio <michal.pecio@gmail.com>
To: Kuangyi Chiang <ki.chiang65@gmail.com>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
mathias.nyman@intel.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xhci: Fix HIK camera control timeout on Etron hosts
Date: Thu, 29 Oct 2026 06:03:35 +0100 [thread overview]
Message-ID: <20261029060335.3ed1fbcf.michal.pecio@gmail.com> (raw)
In-Reply-To: <CAHN5xi1M+g3Sy8YkRKpZuU7EtTxiyi0ZD6y5TCcAZTrpxUpHNw@mail.gmail.com>
On Thu, 29 Oct 2026 10:25:17 +0800, Kuangyi Chiang wrote:
> We did some more testing.
>
> We don't see this issue during device enumeration.
>
> We also found that the timeout is not limited to UVC control
> transfers. In one failure case, the first timeout was observed in
> a UAC control transfer, followed by UVC control transfer timeouts:
>
> [ 961.127402] usb 2-3: 5:2: failed to get current value for ch 0 (-110)
> [ 971.367443] uvcvideo 2-3:1.0: Failed to query (GET_DEF) UVC control
> 2 on unit 2: -110 (exp. 2).
> [ 976.487473] uvcvideo 2-3:1.0: Failed to query (GET_DEF) UVC control
> 3 on unit 2: -110 (exp. 2).
But that's the same device and the same control pipe, right?
So it just failed and we don't know why or whether it was the host or
the device. And this is all during UVC/UAC probe, before any userspace
begins using the device? Or could userspace be involved?
The UVC driver has some aggressive PM; for every userspace ioctl, it
calls usb_autopm_get_interface(), submits an interrupt URB which almost
never completes and unlinks the URB before usb_autopm_put_interface().
Repeated periodic unlinks is a known problem case for many xHCI chips.
FYI, I found that 7c0c31c66a7f9 in v7.3 reduced occurrences of periodic
unlink failures on other junk HW like ASMedia and VIA. Some of those
failures, on ASMedia, resulted in control transfer breakage too.
Have you tried 7.3 yet?
Do you see any interrupt URBs there, using usbmon for example?
> So far, we have reproduced the issue with these xHCI hosts:
>
> ASMedia ASM1142 (1b21:1242)
> Etron EJ168 (1b6f:7023)
> Etron EJ188 (1b6f:7052)
> Intel xHCI (8086:8d31)
I don't know that Intel chip, but the others are quite buggy.
Have you tried other HCs? Any successes?
IME, chips from NEC, Fresco, Renesas are more reliable.
> The camera works with the EHCI host we tested without any additional
> delay.
That's a little suspicious, it may still be an xHCI bug.
Regards,
Michal
prev parent reply other threads:[~2026-10-29 5:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 1:30 [PATCH] xhci: Fix HIK camera control timeout on Etron hosts Kuangyi Chiang
2026-09-14 11:09 ` Michal Pecio
2026-09-16 1:33 ` Kuangyi Chiang
2026-09-16 12:18 ` Mathias Nyman
2026-09-18 1:58 ` Kuangyi Chiang
2026-10-29 2:25 ` Kuangyi Chiang
2026-10-29 5:03 ` Michal Pecio [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=20261029060335.3ed1fbcf.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ki.chiang65@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mathias.nyman@linux.intel.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 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.