linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: michael.moese@men.de (michael.moese at men.de)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX 6 and PCIe DMA issues
Date: Thu, 13 Jul 2017 12:00:31 +0200	[thread overview]
Message-ID: <20170713100031.GA31131@mmlinux> (raw)
In-Reply-To: <20170713090423.GA31807@n2100.armlinux.org.uk>

On Thu, Jul 13, 2017 at 10:04:23AM +0100, Russell King - ARM Linux wrote:
> On Thu, Jul 13, 2017 at 09:07:19AM +0200, michael.moese at men.de wrote:
> > Ok, I hope I am correct. I alloc my memory using dma_alloc_coherent()
> > once, the dma_handle is passed to the device, with no other dma_map*()
> > or dma_sync_*() calls needed?
> 
> Correct.
Great. Thanks for the clarification. I will make sure the usage is done
the right way.

> You must always use the two addresses returned from dma_alloc_coherent()
> and never try to translate them - the DMA address is for programming
> into the hardware, and the virtual address for CPU accesses.  If you do
> try to pass these to the various translators (like virt_to_phys()) the
> result is undefined.

I was trying to just print some addresses for debugging. I removed this
again. I'm just confused, because the DMA device address seems to be the
physical one. At least the memory contains my data. The virtual memory
contains different data. 

Could it be possible this mapping on my board is going wrong?

Michael

  reply	other threads:[~2017-07-13 10:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 13:40 i.MX 6 and PCIe DMA issues Moese, Michael
2017-07-11 14:07 ` Andrew Lunn
2017-07-11 14:50 ` Robin Murphy
2017-07-13  7:07   ` michael.moese at men.de
2017-07-13  9:04     ` Russell King - ARM Linux
2017-07-13 10:00       ` michael.moese at men.de [this message]
2017-07-13 10:18         ` Russell King - ARM Linux
2017-07-13 14:57     ` Robin Murphy
2017-07-14 11:07       ` michael.moese at men.de
2017-07-11 17:56 ` Andrew Lunn

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=20170713100031.GA31131@mmlinux \
    --to=michael.moese@men.de \
    --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).