From: andy@warmcat.com (Andy Green)
To: linux-arm-kernel@lists.infradead.org
Subject: SPI, DMA and an i.MX31
Date: Fri, 25 Sep 2009 08:26:12 +0100 [thread overview]
Message-ID: <4ABC7094.9000701@warmcat.com> (raw)
In-Reply-To: <87077C4F48609F4392621D9F99DDE20901202E06@tesla.star.galaxy.io>
On 09/24/09 11:51, Somebody in the thread at some point said:
Hi Rene -
> The drivers/mmc/host/mxcmmc.c from 2.6.31 uses some different dma api: all
> those fkt start with 'imx_', the sdma's from the ltib have a 'mxc' prefix.
> I tried to match them and wrap those 'mxc' in defines, mapping them to the
> 'imx' ones. Unfortunately for some fkts I didn't find a matching 'mxc' one.
> The driver compiles, but I guess it's pretty useless the way it is. May be
> I should have looked to the driver version in ltib, instead.
>
> After that I tried to register a SDMA channel with a device. As far as I
> can see that works. The Registered channel shows under
> '/proc/sdma/channels'. Freeing that also works.
>
> Next: Will try to start a SDMA transfer with SPI.
Thanks a lot for taking a look at it anyway.
Since this mxcmmc.c imx_ stuff is platform stuff cover mx1 and mx2, I
guess there'll be trouble getting any mx3 DMA stuff accepted that
doesn't play along with its existing game or change them all to some
more standard method.
-Andy
next prev parent reply other threads:[~2009-09-25 7:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 8:26 SPI, DMA and an i.MX31 Wolf, Rene, HRO-GP
[not found] ` <BLU105-W229F8F8F533B107510C600BAE10@phx.gbl>
2009-09-21 8:22 ` Wolf, Rene, HRO-GP
2009-09-21 18:04 ` Magnus Lilja
2009-09-22 2:44 ` Tonyliu
2009-09-22 9:00 ` Wolf, Rene, HRO-GP
2009-09-22 12:23 ` Andy Green
2009-09-22 13:22 ` Wolf, Rene, HRO-GP
2009-09-22 14:10 ` Andy Green
2009-09-22 14:09 ` Magnus Lilja
2009-09-22 16:22 ` Bill Gatliff
2009-09-22 19:45 ` Magnus Lilja
2009-09-24 10:51 ` Wolf, Rene, HRO-GP
2009-09-25 7:26 ` Andy Green [this message]
2009-10-01 10:42 ` Wolf, Rene, HRO-GP
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=4ABC7094.9000701@warmcat.com \
--to=andy@warmcat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.