From: David Brownell <david-b@pacbell.net>
To: "Foale, Jeff" <j-foale@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: OMAP2430: MUSB: Ethernet Gadget Issue
Date: Thu, 6 Dec 2007 08:17:35 -0800 [thread overview]
Message-ID: <200712060817.35806.david-b@pacbell.net> (raw)
In-Reply-To: <F3AC19E99E5D024AB9E6FB2A01683D8A02D46D68@dlee10.ent.ti.com>
On Wednesday 05 December 2007, Foale, Jeff wrote:
>
> I noticed some comments in the musb_gadget.c code:
>
> /* REVISIT for high bandwidth, MUSB_TXCSR_P_INCOMPTX
> * probably rates reporting as a host error
> */
> The MUSB_TXCSR_P_INCOMPTX flag is set on the bad transfer. It seems to
> not be handled correctly (at all).
So it's a silicon or RTL bug then? My generic MUSB docs say:
> > When the endpoint is being used for high-bandwidth Isochronous/Interrupt
> > transfers, this bit is set to indicate where a large packet has been split
> > into 2 or 3 packets for transmission but insufficient IN tokens have been
> > received to send all the parts. Note: In anything other than a high-
> > bandwidth transfer, this bit will always return 0.
Those endpoints aren't high bandwidth, or even ISO/INTR. And yet you
report that bit isn't set to zero ...
- Dave
next prev parent reply other threads:[~2007-12-06 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 22:10 OMAP2430: MUSB: Ethernet Gadget Issue Foale, Jeff
2007-12-06 16:17 ` David Brownell [this message]
2007-12-07 20:55 ` Hunter, Jon
-- strict thread matches above, loose matches on Subject: below --
2007-11-21 17:08 Hunter, Jon
2007-11-23 20:26 ` David Brownell
2007-11-29 20:03 ` Foale, Jeff
2007-11-29 21:07 ` David Brownell
2007-12-07 20:55 ` Hunter, Jon
2007-12-07 20:38 ` Hunter, Jon
2007-12-10 5:34 ` David Brownell
2007-12-12 20:55 ` Hunter, Jon
2007-12-12 23:22 ` Hunter, Jon
2007-12-18 0:00 ` Hunter, Jon
2007-12-18 1:05 ` Tony Lindgren
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=200712060817.35806.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=j-foale@ti.com \
--cc=linux-omap-open-source@linux.omap.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