All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Anurag Kumar Vulisha <anurag.kumar.vulisha@xilinx.com>,
	mathias.nyman@intel.com, gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	anirudh@xilinx.com, Anurag Kumar Vulisha <anuragku@xilinx.com>
Subject: Re: [LINUX PATCH] usb: xhci: Add toggle cycle bit for the last seg trb when cached ring is used
Date: Thu, 1 Jun 2017 16:20:32 +0300	[thread overview]
Message-ID: <593014A0.9010509@linux.intel.com> (raw)
In-Reply-To: <1496238110-4998-1-git-send-email-anuragku@xilinx.com>

On 31.05.2017 16:41, Anurag Kumar Vulisha wrote:
> At present USB 2.0 cameras fail to play when run for 2nd time or greater.
> This issue occurs only when previous endpoint cached ring is used instead
> of allocating a new endpoint ring. The root cause of the problem narrows
> down to the Toggle bit, which is not getting set on the last trb of the
> cached ring last segment. When the controller fetches the last link trb
> with no toggle bit set, abnormal behaviour is generated.
> This patch solves that problem by adding the TOGGLE bit for the last trb
> of the last segment of the cached ring.
>
> Signed-off-by: Anurag Kumar Vulisha <anuragku@xilinx.com>

Thanks, nice catch.

I'm thinking about removing the whole endpoint ring caching instead.

We are using more memory by caching the rings instead of freeing them,
especially as we always try to allocate a new ring and only use the cached
ones when we fail to allocate a new ring.

Would you be willing to test a patch that removes the ring cache completely
with your setup?

Thanks
Mathias  

  reply	other threads:[~2017-06-01 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31 13:41 [LINUX PATCH] usb: xhci: Add toggle cycle bit for the last seg trb when cached ring is used Anurag Kumar Vulisha
2017-06-01 13:20 ` Mathias Nyman [this message]
2017-06-01 16:03   ` Anurag Kumar Vulisha

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=593014A0.9010509@linux.intel.com \
    --to=mathias.nyman@linux.intel.com \
    --cc=anirudh@xilinx.com \
    --cc=anurag.kumar.vulisha@xilinx.com \
    --cc=anuragku@xilinx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.