linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valmiki <valmikibow@gmail.com>
To: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: lorenzo.pieralisi@arm.com, bhelgaas@google.com, robh@kernel.org
Subject: dma-coherent property for PCIe Root
Date: Mon, 14 Sep 2020 10:53:48 +0530	[thread overview]
Message-ID: <1512d7b5-54c6-3b87-0090-5e370955223e@gmail.com> (raw)

Hi All,

How does "dma-coherent" property will work for PCIe as RC on an
ARM SOC ?
Because the end point device drivers are the one which will request dma 
buffers and Root port driver doesn't involve in data path of end point
except for handling interrupts.

How does EP DMA buffers will be hardware coherent if RC driver exposes
dma-coherent property ?

Regards,
Valmiki



             reply	other threads:[~2020-09-14  5:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  5:23 Valmiki [this message]
2020-10-01  5:16 ` dma-coherent property for PCIe Root Jon Masters

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=1512d7b5-54c6-3b87-0090-5e370955223e@gmail.com \
    --to=valmikibow@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=robh@kernel.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).