From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: George Cherian <george.cherian@ti.com>
Cc: linux-usb@vger.kernel.org, balbi@ti.com,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH] usb: host: xhci-plat: Enable XHCI_SPURIOUS_SUCCESS quirk for xhci-plat
Date: Sun, 30 Jun 2013 14:00:28 -0700 [thread overview]
Message-ID: <20130630210028.GB4946@xanatos> (raw)
In-Reply-To: <20130626165334.GA19462@xanatos>
On Wed, Jun 26, 2013 at 09:53:34AM -0700, Sarah Sharp wrote:
> On Wed, Jun 26, 2013 at 02:28:57PM +0530, George Cherian wrote:
> > Synopsis xhci controllers with hci_version > 0.96 gives spurious success
> > events on short packet completion. During webcam capture the
> > "ERROR Transfer event TRB DMA ptr not part of current TD" was observed.
> > The same application works fine with synopsis controllers hci_version 0.96.
>
> It's a known issue. The xHCI 1.0 spec changed how hardware handles
> short packets. The HW will notify SW of the TRB where the short packet,
> and it will also give a successful status for the last TRB in a TD (the
> one with the IOC flag set). On the second successful status, that
> warning will be triggered in the driver.
>
> Software is now supposed to not assume the TD as done until it gets that
> last successful status. That means we have a slight race condition,
> although it should have little practical impact. This patch papers over
> that issue.
>
> I will take this patch, but will add the note that is on my long-term
> to-do list to fix this issue.
Actually, since it applies to both xhci-plat and xhci-pci hosts, can you
move setting this quirk into xhci_gen_setup?
Sarah Sharp
> > Signed-off-by: George Cherian <george.cherian@ti.com>
> > ---
> > drivers/usb/host/xhci-plat.c | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git a/drivers/usb/host/xhci-plat.c b/drivers/usb/host/xhci-plat.c
> > index 93ad67e..e63c6d3 100644
> > --- a/drivers/usb/host/xhci-plat.c
> > +++ b/drivers/usb/host/xhci-plat.c
> > @@ -25,6 +25,16 @@ static void xhci_plat_quirks(struct device *dev, struct xhci_hcd *xhci)
> > * dev struct in order to setup MSI
> > */
> > xhci->quirks |= XHCI_BROKEN_MSI;
> > +
> > + /*
> > + * In some xhci controllers which follows xhci 1.0 spec gives a spurious
> > + * success event after a short transfer. This quirk will ignore such
> > + * spurious event. Hit this issue in synopsis xhci controllers with
> > + * hci_version > 0.96
> > + */
> > +
> > + if (xhci->hci_version > 0x96)
> > + xhci->quirks |= XHCI_SPURIOUS_SUCCESS;
> > }
> >
> > /* called during probe() after chip reset completes */
> > --
> > 1.8.1.4
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-usb" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-06-30 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 8:58 [PATCH] usb: host: xhci-plat: Enable XHCI_SPURIOUS_SUCCESS quirk for xhci-plat George Cherian
2013-06-26 9:02 ` Felipe Balbi
2013-06-26 12:16 ` George Cherian
2013-06-26 12:25 ` Felipe Balbi
2013-06-26 16:53 ` Sarah Sharp
2013-06-30 21:00 ` Sarah Sharp [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=20130630210028.GB4946@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=balbi@ti.com \
--cc=george.cherian@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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