From: Kuangyi Chiang <ki.chiang65@gmail.com>
To: mathias.nyman@intel.com, gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
ki.chiang65@gmail.com
Subject: [PATCH] xhci: Fix HIK camera control timeout on Etron hosts
Date: Mon, 14 Sep 2026 09:30:33 +0800 [thread overview]
Message-ID: <20260914013033.3938-1-ki.chiang65@gmail.com> (raw)
Control transfers to the HIK 1080P Camera (2bdf:0280) can time out when
the device is connected through an Etron xHCI host:
[ 48.363671] uvcvideo: Found UVC 1.00 device HIK 1080P Camera (2bdf:0280)
[ 53.465662] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
[ 58.585653] uvcvideo: Failed to query (129) UVC probe control : -110 (exp. 26).
[ 58.592967] uvcvideo: Failed to initialize the device (-5).
Testing shows that at least 125 us between control transfers is required
to avoid the timeout. Limit the workaround to the affected Etron host and
USB device combination to avoid changing control-transfer timing for other
devices.
Perform the delay before taking xhci->lock so the existing state validation
and TD queueing remain in the same critical section. Use udelay() because
urb_enqueue() may be called from atomic context and cannot use a sleeping
delay.
Signed-off-by: Kuangyi Chiang <ki.chiang65@gmail.com>
---
drivers/usb/host/xhci.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index 5c759ad..925716a 100644
--- a/drivers/usb/host/xhci.c
+++ b/drivers/usb/host/xhci.c
@@ -1648,6 +1648,16 @@ static int xhci_urb_enqueue(struct usb_hcd *hcd, struct urb *urb, gfp_t mem_flag
trace_xhci_urb_enqueue(urb);
+ /*
+ * This camera needs at least 125 us between control transfers
+ * when used with an Etron xHCI host.
+ */
+ if ((xhci->quirks & XHCI_ETRON_HOST) &&
+ usb_endpoint_xfer_control(&urb->ep->desc) &&
+ le16_to_cpu(urb->dev->descriptor.idVendor) == 0x2bdf &&
+ le16_to_cpu(urb->dev->descriptor.idProduct) == 0x0280)
+ udelay(125);
+
spin_lock_irqsave(&xhci->lock, flags);
ret = xhci_check_args(hcd, urb->dev, urb->ep,
--
2.25.1
next reply other threads:[~2026-09-14 1:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 1:30 Kuangyi Chiang [this message]
2026-09-14 11:09 ` Michal Pecio
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=20260914013033.3938-1-ki.chiang65@gmail.com \
--to=ki.chiang65@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®