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: Fri, 14 Jul 2017 13:07:37 +0200	[thread overview]
Message-ID: <20170714110737.GA17229@mmlinux> (raw)
In-Reply-To: <37eec44d-2157-1f11-681f-7fbc50983d62@arm.com>

On Thu, Jul 13, 2017 at 03:57:19PM +0100, Robin Murphy wrote:
> >> I don't much like the sound of that "and" there - coherent DMA
> >> allocations are, as the name implies, already coherent for CPU and DMA
> >> accesses, and require no maintenance; the streaming DMA API
> >> (dma_{map,unmap,sync}_*) on the other hand is *only* for use on
> >> kmalloced memory.
I removed all the calls to dma_{map,unmap,sync}_* and took special care
on the handling of the dma_attr_t's. I now dma_alloc_coherent my memory,
and do nothing else with the dma_attr_t's. It seems to work, at least
partly, now. I had to grab a newer board, because we killed it while
soldering wires to trace PCI Express traffic.

Maybe I had some weird old CPU or some strange U-Boot or I simply missed
removing all dma_sync_* calls or similar before.

Now I got other issues, but at least the DMA seems to be working now.
Thanks to you, I think I understood this topic now, thank you.

Now I can try to figure out why a read to the PCI Express may stop all
traffic - that's a different story.


Thanks,
Michael

  reply	other threads:[~2017-07-14 11:07 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
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 [this message]
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=20170714110737.GA17229@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).