public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Roger Quadros <rogerq@ti.com>, mathias.nyman@intel.com
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] usb: xhci: bInterval quirk for TI TUSB73x0
Date: Wed, 22 Mar 2017 15:06:44 +0200	[thread overview]
Message-ID: <58D276E4.80607@linux.intel.com> (raw)
In-Reply-To: <787d6f0f-d69c-ba4a-8892-b3558c005184@ti.com>

On 22.03.2017 13:43, 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 and
> unplugged several times on a TUSB73x0 XHCI host.
>
> 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>
> ---

Added to my for-usb-next queue.

Thanks
-Mathias

      reply	other threads:[~2017-03-22 13:05 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
2017-03-22 11:43       ` [PATCH v3] " Roger Quadros
2017-03-22 13:06         ` Mathias Nyman [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=58D276E4.80607@linux.intel.com \
    --to=mathias.nyman@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=rogerq@ti.com \
    --cc=sergei.shtylyov@cogentembedded.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