All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Tony Lindgren <tony@atomide.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: DMA example
Date: Wed, 24 Feb 2010 18:24:13 -0800	[thread overview]
Message-ID: <4B85DF4D.9020007@balister.org> (raw)
In-Reply-To: <20100224225231.GA28173@atomide.com>

On 02/24/2010 02:52 PM, Tony Lindgren wrote:
> * Philip Balister<philip@balister.org>  [100224 14:28]:
>> On 02/24/2010 12:35 PM, Tony Lindgren wrote:
>>> * Philip Balister<philip@balister.org>   [100224 11:31]:
>>>> I am trying to setup a dma operation to copy memory from GPMC
>>>> address space into RAM. The only examples using the omap-dma api use
>>>> hardware triggers.
>>>>
>>>> When I start a transfer, I end up with a DMA transaction error when
>>>> I start the transfer.
>>>>
>>>> Does anyone have a good example of a software transfer? Currently, I
>>>> am tracing the omap dma api to see how things map into the registers
>>>> ....
>>>
>>> Enjoy the GPMC timings. I recommend attaching a logic analyzer there
>>> to verify the things are right for the key lines if you have chance.
>>>
>>> Hmm I thought the hardware triggers were optional in at least
>>> drivers/usb/musb/tusb6010_omap.c.. Maybe I don't remember correctly.
>>
>> GPMC is easy :)
>
> Sounds like you just got lucky! :)

OK, I am using the 2K non-multiplexed mode atm :) Still I have a logic 
analyzer and am confident I can get the mux'd modes working. Burst is 
still a bit scary.

>> Basically, I have a device attached to a GPMC chip select and I need
>> to read/write to it. The GPNC bit is fine, we'd just like to use the
>> DMA controller to move the data.
>
> That should work, at least there has been several memory-to-memory
> dma test modules posted here over the years. Have you tried using
> OMAP_DMA_NO_DEVICE for omap_request_dma? Also search for omap dmatest
> or similar.

Thanks. This is suggesting I am on the right track, but the transfer 
still fails with: DMA transaction error with device 0.

The call to omap_set_dma_transfer_params adds these two args:

params->trigger, params->src_or_dst_synch);

I think they are more for hw synched transfers and set them to zero.

the src|dest param setting calls added the  params->src_ei, 
params->src_fi arguments. I've set these to 1.

Any more clues?

Philip

  reply	other threads:[~2010-02-25  2:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 19:34 DMA example Philip Balister
2010-02-24 20:35 ` Tony Lindgren
2010-02-24 22:31   ` Philip Balister
2010-02-24 22:52     ` Tony Lindgren
2010-02-25  2:24       ` Philip Balister [this message]
2010-02-25  4:26         ` Philip Balister
2010-02-25  4:59           ` Shilimkar, Santosh
2010-02-25  6:22         ` Venkatraman S
2010-02-24 20:48 ` Shilimkar, Santosh

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=4B85DF4D.9020007@balister.org \
    --to=philip@balister.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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 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.