All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Vikram Pandita <vikram.pandita@ti.com>
Cc: stern@rowland.harvard.edu, linux-usb@vger.kernel.org,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH] usb: ehci: report Data Buffer Error in debug mode
Date: Sat, 29 Oct 2011 02:22:22 +0200	[thread overview]
Message-ID: <201110290222.22990.marek.vasut@gmail.com> (raw)
In-Reply-To: <1319846874-10106-1-git-send-email-vikram.pandita@ti.com>

> From: Vikram Pandita <vikram.pandita@ti.com>
> 
> Data Buffer Error as per spec section 4.15.1.1.2
> results when there is Underrun or Overrun condition.
> 
> This error is considered non-fatal and never gets reported.
> Its a very good indication on things going wrong at system level,
> like running memory at much slower speed.
> 
> This is a good error to flag allowing system level corrections.
> 
> An issue was found with OMAP4460 board where DDR had to be run
> at full speed and this logging helped.
> 
> Signed-off-by: Vikram Pandita <vikram.pandita@ti.com>
> ---
>  drivers/usb/host/ehci-q.c |   14 ++++++++++++++
>  1 files changed, 14 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/usb/host/ehci-q.c b/drivers/usb/host/ehci-q.c
> index 4e4066c..2451361 100644
> --- a/drivers/usb/host/ehci-q.c
> +++ b/drivers/usb/host/ehci-q.c
> @@ -373,6 +373,20 @@ qh_completions (struct ehci_hcd *ehci, struct ehci_qh
> *qh) retry_xacterr:
>  		if ((token & QTD_STS_ACTIVE) == 0) {
> 
> +			/* Report Data Buffer Error: non-fatal but useful */
> +			if (token & QTD_STS_DBE) {
> +
> +				ehci_dbg(ehci,
> +				"detected DataBufferErr %s for urb %p ep%d%s len 
%d, qtd %p [qh
> %p]\n", +				(urb->ep->desc.bEndpointAddress & 
USB_DIR_IN) ?
> +						"OVER-RUN" : "UNDER-RUN",
> +				urb, urb->ep->desc.bEndpointAddress & 0x0f,
> +				(urb->ep->desc.bEndpointAddress & USB_DIR_IN) ? 
"in" : "out",
> +				urb->transfer_buffer_length,
> +				qtd, urb->ep->hcpriv);
> +
> +			}
> +
>  			/* on STALL, error, and short reads this urb must
>  			 * complete and all its qtds must be recycled.
>  			 */

Looks basically ok to me.

Reviewed-by: Marek Vasut <marek.vasut@gmail.com>

  reply	other threads:[~2011-10-29  0:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29  0:07 [PATCH] usb: ehci: report Data Buffer Error in debug mode Vikram Pandita
2011-10-29  0:22 ` Marek Vasut [this message]
     [not found] ` <1319846874-10106-1-git-send-email-vikram.pandita-l0cyMroinI0@public.gmane.org>
2011-10-29 17:00   ` Alan Stern

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=201110290222.22990.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=vikram.pandita@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 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.