All of lore.kernel.org
 help / color / mirror / Atom feed
From: adam.cottrel@veea.com (Adam Cottrel)
To: linux-arm-kernel@lists.infradead.org
Subject: DMA remote memcpy requests
Date: Mon, 15 Oct 2018 15:51:21 +0000	[thread overview]
Message-ID: <DM6PR04MB405906FA74124FFEBCA9188AF2FD0@DM6PR04MB4059.namprd04.prod.outlook.com> (raw)
In-Reply-To: <20181015153926.GC8789@hc>

Dear Jan,

> I'm not sure where that point would be where DMA request could be lost
> here.
> The MMC and PCIe only meet in the NCB (near coprocessor bus) which goes
> to the Coherent memory interconnect and L2 cache.
> 
> I've looked for any known errata but didn't find anything that would match
> your problem.

For the purposes of debug, is it possible for me to turn off the MMC? Or the L2 cache? Or put it into pass through mode? Or get any kind of stack trace on its operation?

Best,
Adam

  reply	other threads:[~2018-10-15 15:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11  7:28 DMA remote memcpy requests Adam Cottrel
2018-10-12  9:09 ` Will Deacon
2018-10-12  9:48   ` Adam Cottrel
2018-10-12 10:46     ` Robin Murphy
2018-10-12 11:06       ` Adam Cottrel
2018-10-15 14:34       ` Adam Cottrel
2018-10-15 15:09         ` Jan Glauber
2018-10-15 15:24           ` Adam Cottrel
2018-10-15 15:39             ` Jan Glauber
2018-10-15 15:51               ` Adam Cottrel [this message]
2018-10-18 15:36                 ` Adam Cottrel
2018-10-22 14:28                   ` Jan Glauber
2018-10-22 14:39                     ` Adam Cottrel
2018-10-22 15:33                       ` Jan Glauber
     [not found]         ` <DM6PR07MB4923F3328079199090D6D2CA9EFE0@DM6PR07MB4923.namprd07.prod.outlook.com>
2018-10-16 16:52           ` Adam Cottrel
2018-10-16 17:08             ` Robin Murphy
2018-10-12 11:03     ` Jan Glauber
2018-10-12 11:07       ` Adam Cottrel

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=DM6PR04MB405906FA74124FFEBCA9188AF2FD0@DM6PR04MB4059.namprd04.prod.outlook.com \
    --to=adam.cottrel@veea.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.