From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Roger Quadros <rogerq@ti.com>, mathias.nyman@intel.com
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] usb: xhci: bInterval quirk for TI TUSB73x0
Date: Mon, 13 Mar 2017 11:44:00 +0300 [thread overview]
Message-ID: <d7f66116-dea0-eda9-2cba-4a9f61b78435@cogentembedded.com> (raw)
In-Reply-To: <9de96f48-1570-974a-2ceb-acf051a80e6b@ti.com>
Hello!
On 3/13/2017 11:11 AM, Roger Quadros wrote:
> As per [1] issue #4,
> "The periodic EP scheduler always tries to schedule the EPs
> that have large intervals (interval equal to or greater than
> 128 microframes) into different microframes. So it maintains
> an internal counter and increments for each large interval
> EP added. When the counter is greater than 128, the scheduler
> rejects the new EP. So when the hub re-enumerated 128 times,
> it triggers this condition."
>
> This results in Bandwidth error when devices with periodic
> endpoints (ISO/INT) having bInterval > 7 are plugged an
s/an/and/.
> unplugged several times on a TUSB73x0 xhci host.
xHCI.
> Workaround this issue by limiting the bInterval to 7
> (i.e. interval to 6) for High-speed or faster periodic endpoints.
>
> [1] - http://www.ti.com/lit/er/sllz076/sllz076.pdf
>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
[...]
MBR, Sergei
next prev parent reply other threads:[~2017-03-13 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 8:47 [PATCH] usb: xhci: bInterval quirk for TI TUSB73x0 Roger Quadros
2017-03-09 9:44 ` Sergei Shtylyov
2017-03-10 16:04 ` Roger Quadros
2017-03-13 8:11 ` [PATCH v2] " Roger Quadros
2017-03-13 8:44 ` Sergei Shtylyov [this message]
2017-03-22 11:43 ` [PATCH v3] " Roger Quadros
2017-03-22 13:06 ` 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=d7f66116-dea0-eda9-2cba-4a9f61b78435@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=rogerq@ti.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).