mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: Hans de Goede <hansg@kernel.org>
Cc: Kuangyi Chiang <ki.chiang65@gmail.com>,
	laurent.pinchart@ideasonboard.com, mchehab@kernel.org,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: uvcvideo: Add UVC_QUIRK_CTL_MSG_DELAY_1M for HIK camera
Date: Thu, 5 Nov 2026 10:33:47 +0100	[thread overview]
Message-ID: <20261105103347.4983b901.michal.pecio@gmail.com> (raw)
In-Reply-To: <7c254ab7-579e-4c17-80fb-596e6fdd29a9@kernel.org>

Hi Hans,

Kuangyi Chiang has also reported this to linux-usb and linked here.

On Thu, 29 Oct 2026 13:46:04 +0100, Hans de Goede wrote:
> Is this a USB-2.0 camera connected to a XHCI controller ?
> 
> And if yes, how old is this camera model ?
> 
> The reason why I'm asking this is because the EHCI USB-2.0 controller
> interface causes a natural delay between consecutive ctrl commands
> queued one by one till the start of the next USB frrame, so they get
> spaced 1 ms apart.
> 
> Where as the modern XHCI controller interface will put these
> back-to-back on the USB bus. We've seen some issues with (older) USB
> devices before where they needed some delay because they were
> originally only validated with EHCI controllers and the hw/ff assumes
> it will get some "breathing space" between control messages.

Are you sure that this wasn't possible with EHCI at all?

What sort of devices were affected? A bit surprising to see that there
is apparently no quirk for a known issue.

Regards,
Michal

      parent reply	other threads:[~2026-11-05  9:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  3:31 Kuangyi Chiang
2026-10-29  8:56 ` Laurent Pinchart
2026-11-03  1:08   ` Kuangyi Chiang
2026-10-29 12:46 ` Hans de Goede
2026-11-03  1:18   ` Kuangyi Chiang
2026-11-05  9:33   ` 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=20261105103347.4983b901.michal.pecio@gmail.com \
    --to=michal.pecio@gmail.com \
    --cc=hansg@kernel.org \
    --cc=ki.chiang65@gmail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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

all inboxes | Powered by JetHome®