From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: MUSB multiplatform work?
Date: Thu, 30 May 2013 13:31:33 -0700 [thread overview]
Message-ID: <20130530203132.GC6467@atomide.com> (raw)
In-Reply-To: <CACRpkdZHupVFS+pNADpaJjunPa3fEtyCqLwbL-etHs3gt8EW0Q@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [130530 13:27]:
> On Thu, May 30, 2013 at 10:18 PM, Tony Lindgren <tony@atomide.com> wrote:
>
> > TUSB would work with dmaengine, but AFAIK we're still missing the
> > dmaengine configuration options to support increasing device end
> > FIFO address.
>
> Can you elaborate on this? What is the usecase here?
There are many devices where the device FIFO is memory mapped to the
GPMC bus on omaps, like TUSB, OneNAND, smc911x etc. I believe the
only reason why these have not been converted to the dmaengine is
the fact that dmaengine cannot configure the DMA hardware to do
autoincrement and loop over the device FIFO.
You can see an example of this in tusb_omap_dma_program() if you
look at the various dma_params entries and omap_set_dma_* functions.
Regards,
Tony
next prev parent reply other threads:[~2013-05-30 20:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 15:02 MUSB multiplatform work? Arnd Bergmann
2013-05-28 16:35 ` Felipe Balbi
2013-05-30 20:18 ` Tony Lindgren
2013-05-30 20:21 ` Linus Walleij
2013-05-30 20:31 ` Tony Lindgren [this message]
2013-05-30 21:19 ` Linus Walleij
2013-06-12 10:05 ` Vinod Koul
2013-06-12 11:57 ` Jassi Brar
2013-06-17 13:43 ` Vinod Koul
2013-06-17 15:57 ` Jassi Brar
2013-06-01 11:41 ` Jassi Brar
2013-05-30 20:54 ` Tony Lindgren
2013-05-31 4:00 ` Felipe Balbi
2013-05-31 17:52 ` 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=20130530203132.GC6467@atomide.com \
--to=tony@atomide.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).