public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: "Hunter, Jon" <jon-hunter@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: OMAP2430: MUSB: Ethernet Gadget Issue
Date: Sun, 9 Dec 2007 21:34:23 -0800	[thread overview]
Message-ID: <200712092134.23712.david-b@pacbell.net> (raw)
In-Reply-To: <5573C19A4BBDB441BED2A44157E9705302C29F01@dlee12.ent.ti.com>

On Friday 07 December 2007, Hunter, Jon wrote:
> ep1in (hw1): 1buf dma, csr b404 maxp 0200

That's the same for both UDP and TCP cases:

  8000 - AutoSet TxPktRdy after loading a complete packet
  2000 - Mode TX (probably irrelevant here)
  1000 - DMAReqEnab
  0400 - DMAReqMode 1 (vs 0)
  0004 - Underrun ... got IN packet with empty fifo

And the queues are sitting there with packets marked as
having transmitted no bits.

That underrun bit looks suspicious.  ISTR having issues
with it before; it's stupid, there's basically no point
in the hardware even reporting such a routine case (no
sane driver could afford to care about it); it's only
there to cause trouble.

Understanding that the x430 uses Mentor's DMA engine
and that code has AFAIK not been stressed ... maybe it
has to learn more about how to ignore bogus faults.

I don't see signs of the 0080 Incomptx bit being set.


> ep1out (hw1): 1buf dma, csr 2003 maxp 0200
>        req c1e9a8e0, 512/1536

Again, same for UDP and TCP.

 0200 - DmaReqEnab (note gratuitous difference from TX side)
 0002 - FifoFull
 0001 - RxPktRdy

There what's odd is that nothing seems to have emptied the
FIFO.  I've not looked at the Mentor DMA engine, but I'd kind
of hope that it's more sane than CPPI ... so that one could
let it offload entire IEEE 802 packets without needing to
wake up the CPU after each packet.

You did say the issue was on the TX side, not the RX side?
The "obvious problem" here is on the RX side, not TX...

- Dave

  reply	other threads:[~2007-12-10  5:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 17:08 OMAP2430: MUSB: Ethernet Gadget Issue 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2007-12-05 22:10 Foale, Jeff
2007-12-06 16:17 ` David Brownell
2007-12-07 20:55   ` Hunter, Jon

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=200712092134.23712.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=jon-hunter@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