linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Jan Schmidt <jan@centricular.com>, linux-usb@vger.kernel.org
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: Re: [PATCH] xhci: Check all endpoints for LPM timeout
Date: Thu, 12 Sep 2019 17:14:38 +0200	[thread overview]
Message-ID: <1568301278.3069.7.camel@pengutronix.de> (raw)
In-Reply-To: <20190912144921.368-1-jan@centricular.com>

On Fri, 2019-09-13 at 00:49 +1000, Jan Schmidt wrote:
> If an endpoint is encountered that returns USB3_LPM_DEVICE_INITIATED, keep
> checking further endpoints, as there might be periodic endpoints later
> that return USB3_LPM_DISABLED due to shorter service intervals.
> 
> Without this, the code can set too high a maximum-exit-latency and
> prevent the use of multiple USB3 cameras that should be able to work.
> 
> Signed-off-by: Jan Schmidt <jan@centricular.com>
> Tested-by: Philipp Zabel <p.zabel@pengutronix.de>

This fixes the capture from multiple Oculus Sensors, as described in the
"Not enough bandwidth with Magewell XI100DUSB-HDMI" thread:

https://lore.kernel.org/linux-usb/CA+gwMce-h9LPCv1hhfEcRz_2w9mEQLOjy42dcjvPxTeawSU5kQ@mail.gmail.com/

regards
Philipp

  reply	other threads:[~2019-09-12 15:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-12 14:49 [PATCH] xhci: Check all endpoints for LPM timeout Jan Schmidt
2019-09-12 15:14 ` Philipp Zabel [this message]
2019-09-13 12:58 ` Mathias Nyman
2019-09-13 13:46   ` Jan Schmidt
2019-09-17 14:53     ` [RFT PATCH] xhci: Prevent device initiated U1/U2 link pm if exit latency is too long Mathias Nyman
2019-09-17 15:56       ` Jan Schmidt
2019-09-18 12:46         ` Mathias Nyman

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=1568301278.3069.7.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=jan@centricular.com \
    --cc=linux-usb@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).