From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] usb: ehci: make HC see up-to-date qh/qtd descriptor ASAP
Date: Fri, 02 Sep 2011 10:50:58 +0100 [thread overview]
Message-ID: <4E60A702.1060504@arm.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF04B327A383@HQMAIL01.nvidia.com>
On 01/09/11 20:08, Stephen Warren wrote:
> Marc Dietich wrote at Thursday, September 01, 2011 5:14 AM:
>> I'll add Stephen Warren from NVIDIA to the CC list. He has more HW to test on.
>
> Here are the results I found:
>
> Harmony:
> Tegra USB3 -> SMSC9514 hub: NOT affected
> (Unplugging LAN cable, or disabling SMSC9514 LAN driver doesn't change this)
>
> Seaboard (springbank; clamshell):
> Tegra USB1 -> no hub: Affected
>
> Seaboard (seaboard non-clamshell):
> Tegra USB1 -> no hub: Affected
> Tegra USB3 -> no hub: Affected
>
> TrimSlice:
> Tegra USB3 -> unknown hub: Affected
>
> This implies there's something different about Harmony.
>
> Is the USB hub a clue? Seaboard doesn't have one, and although I don't
> know what model TrimSlice uses, I assume it's different since I know
> TrimSlice's Ethernet is not the same as Harmony's.
Panda has the exact same USB hub configuration, and is affected. So we
can rule this out.
> I don't see anything in board-harmony.c vs. board-seaboard.c that'd affect
> anything USB-related.
>
> Perhaps there's some kind of bootloader or BCT difference. However, my
> Harmony and both Seaboards both use (a very old) U-Boot and BCT from
> ChromeOS, so I don't imagine there's actually much difference there.
I just noticed something else. Harmony is fast *most of the time*. In
about one in 3 reboots, I get the slow behavior. When USB is fast, I
also have I2C interrupts "screaming":
85: 294321 0 GIC tegra-i2c
116: 0 0 GIC tegra-i2c
118: 98542 0 GIC tps6586x
This is a couple of seconds after boot.
When USB is slow, I see the following:
[ 0.385270] tps6586x 3-0034: Chip ID read failed: -121
[ 0.390584] tps6586x: probe of 3-0034 failed with error -5
... and I2C interrupt is quiet.
The I2C interrupt handler calls writel(), which does a cache sync. That
would explain the "fast" behavior of Harmony.
Do you see the same this on your board?
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2011-09-02 9:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 16:03 [PATCH] usb: ehci: make HC see up-to-date qh/qtd descriptor ASAP ming.lei at canonical.com
2011-08-30 16:15 ` Alan Stern
2011-08-30 16:38 ` Mark Salter
2011-08-30 17:15 ` Alan Stern
2011-08-30 18:45 ` Mark Salter
2011-08-30 17:26 ` Will Deacon
2011-08-30 17:48 ` Greg KH
2011-08-30 17:54 ` Will Deacon
2011-08-31 0:23 ` Chen Peter-B29397
2011-08-31 8:49 ` Will Deacon
2011-08-31 12:33 ` Chen Peter-B29397
2011-08-31 13:43 ` Mark Salter
2011-08-31 15:21 ` Will Deacon
2011-08-31 15:27 ` Mark Salter
2011-08-31 16:12 ` Marc Zyngier
2011-08-31 16:55 ` Marc Dietrich
2011-09-01 10:34 ` Marc Zyngier
2011-09-01 11:13 ` Marc Dietich
2011-09-01 19:08 ` Stephen Warren
2011-09-02 9:50 ` Marc Zyngier [this message]
2011-09-02 17:07 ` Stephen Warren
2011-09-02 11:13 ` Marc Dietich
2011-08-31 17:46 ` Nicolas Pitre
2011-08-31 17:51 ` Will Deacon
2011-08-31 18:19 ` Rob Herring
2011-08-31 18:35 ` Mark Salter
2011-08-31 18:49 ` Rob Herring
2011-08-31 18:58 ` Mark Salter
2011-08-31 19:35 ` Will Deacon
2011-09-08 22:41 ` Mark Salter
2011-10-31 6:49 ` Pandita, Vikram
2011-08-31 0:56 ` Ming Lei
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=4E60A702.1060504@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).