From: David Brownell <david-b@pacbell.net>
To: Nazim Khan <nazim.asad@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [Question] Always got STALL in MUSB Host driver
Date: Sun, 18 Nov 2007 22:34:15 -0800 [thread overview]
Message-ID: <200711182234.16066.david-b@pacbell.net> (raw)
In-Reply-To: <ef9503490711182208yee319c6rf80245426d9ce1d9@mail.gmail.com>
On Sunday 18 November 2007, Nazim Khan wrote:
> Hi Dave,
>
> Was that in DMA mode or PIO Mode?
Probably PIO, since that's usually the first stage of
debugging given a choice of modes.
I vaguely recall it was one of those two modes, but
don't recall which one. If it was DMA, I sure don't
recall which of the several DMA engine wass involved. ;)
- Dave
> regards,
> Nazim
>
> On Nov 16, 2007 12:13 AM, David Brownell <david-b@pacbell.net> wrote:
> > On Thursday 15 November 2007, Tony Lindgren wrote:
> > > Hmm, I never got double buffering to reliably work on tusb as far as I
> > > remember. I guess Dave got it working on DaVinci, so maybe he has some
> > > pointers.
> >
> > It's been some time since I tried that. What I vaguely recall
> > is that it worked on the peripheral side, but on the host side
> > there was a issue if for example both sides (tx, rx) of a given
> > FIFO tried to do things at the same time.
> >
> > The driver code has improved a lot since I saw those failures,
> > so I wouldn't trust those memories to indicate anything specific
> > about current behavior.
> >
> > - Dave
> >
>
next prev parent reply other threads:[~2007-11-19 6:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 10:48 [Question] Always got STALL in MUSB Host driver Bryan Wu
2007-11-15 18:01 ` Tony Lindgren
2007-11-15 18:43 ` David Brownell
2007-11-19 6:08 ` Nazim Khan
2007-11-19 6:34 ` David Brownell [this message]
2007-11-19 6:49 ` Nazim Khan
2007-11-19 7:23 ` David Brownell
2007-11-19 10:25 ` Nazim Khan
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=200711182234.16066.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.com \
--cc=nazim.asad@gmail.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