From: ryan@bluewatersys.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: ep93xx SPI driver v3
Date: Mon, 19 Apr 2010 08:53:28 +1200 [thread overview]
Message-ID: <4BCB7148.5040600@bluewatersys.com> (raw)
In-Reply-To: <r2j56d259a01004162023tdf8f226aw5aab98bd54c03ac0@mail.gmail.com>
Martin Guy wrote:
> cc-ing to list...
>
>> Next thing (after possible bug fixes, that is) is probably to
>> implement proper DMA support. Unfortunately there is no platform
>> code for that yet, only M2P controller support :( which means that
>> we have to implement M2M controller support
>
> Yes, ep93xx DMA engine has two flavours: memory-to-peripheral, used
> for most devices, and memory-to-memory, used for block memcpy and for
> memory-to-SSP/SPI (== SD card).
>
> The easiest route would seem to be to get the M2M stuff working to do
> memcpy fast. Can linux make use of that? I haven't yet seen anything
> that can make use of a memory-to-memory copy DMA engine.
There is support for the M2P DMA (see arch/arm/mach-ep93xx/dma-m2p.c),
which could be used as a guide. There is also dmaengine, which I don't
know much about, but could possibly be implemented for the ep93xx DMA
channels. I think dmaengine supports asynchronous memcpy.
> If we can get that working, a reasonable second stage would make it
> work for ep93xx-SPI transfers, making SD card access even less
> CPU-intensive
Sine the M2M DMA support for the ep93xx is not in the mainline yet, I
would be happy for the SPI driver to be merged without DMA support, and
to have it added at a later date.
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan at bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
next prev parent reply other threads:[~2010-04-18 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100415173905.GJ2685@gw.healthdatacare.com>
[not found] ` <j2u56d259a01004151645y47ec8254ree59189aaa6b5baa@mail.gmail.com>
[not found] ` <20100416042658.GK2685@gw.healthdatacare.com>
[not found] ` <l2p56d259a01004160211m17bc0f10gc63a5ca82436c8e3@mail.gmail.com>
[not found] ` <20100416094444.GC6718@gw.healthdatacare.com>
[not found] ` <p2l56d259a01004160455jdf290557yd102cf78d9f1252e@mail.gmail.com>
[not found] ` <20100416171032.GD6718@gw.healthdatacare.com>
2010-04-17 3:23 ` ep93xx SPI driver v3 Martin Guy
2010-04-17 5:15 ` Mika Westerberg
2010-04-18 20:53 ` Ryan Mallon [this message]
2010-04-19 6:48 ` Mika Westerberg
2010-04-19 9:25 ` Martin Guy
2010-04-19 9:55 ` Mika Westerberg
2010-04-19 19:38 ` Ryan Mallon
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=4BCB7148.5040600@bluewatersys.com \
--to=ryan@bluewatersys.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