From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 0/3] How to pass IOMMU map attr via DMA API?
Date: Mon, 24 Jun 2013 09:21:28 +0200 [thread overview]
Message-ID: <20130624072128.GP11309@8bytes.org> (raw)
In-Reply-To: <20130624081759.76e66d42bbf7c2c54ed1975c@nvidia.com>
On Mon, Jun 24, 2013 at 08:17:59AM +0300, Hiroshi Doyu wrote:
> Ok, thanks. One more question, IOMMU H/W sometimes supports more
> platform specific attributes than READ/WRITE. For example, in OMAP,
>
> #define IOMMU_FLAG (IOVMF_ENDIAN_LITTLE | IOVMF_ELSZ_8)
>
> Is there any way to deal with those platform specific attrs from DMA
> mapping API POV?
Depends on the kind of flag and whether you want to make it changeable
from the DMA-API. The AMD IOMMU for example has a flag in the
page-tables to force PCI DMA coherency. This is always set by the
driver.
For other parameters that should be changeable and don't fit into the
dma_direction parameter in some way the use of dma_attr would make
sense.
Joerg
prev parent reply other threads:[~2013-06-24 7:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 5:49 [RFC 0/3] How to pass IOMMU map attr via DMA API? Hiroshi Doyu
[not found] ` <1371707384-30037-4-git-send-email-hdoyu@nvidia.com>
2013-06-20 6:50 ` [Linaro-mm-sig] [RFC 3/3] iommu/tegra: smmu: Support read-only mapping Kyungmin Park
2013-06-20 7:27 ` Hiroshi Doyu
[not found] ` <1371707384-30037-3-git-send-email-hdoyu@nvidia.com>
2013-06-20 8:07 ` [Linaro-mm-sig] [RFC 2/3] ARM: dma-mapping: Pass DMA attrs as IOMMU prot Nishanth Peethambaran
2013-06-20 8:24 ` Hiroshi Doyu
2013-06-20 8:55 ` Nishanth Peethambaran
2013-06-20 9:54 ` Hiroshi Doyu
2013-06-20 10:13 ` Arnd Bergmann
2013-06-20 10:34 ` Hiroshi Doyu
2013-06-20 10:57 ` Arnd Bergmann
2013-06-20 12:49 ` Nishanth Peethambaran
2013-06-20 9:31 ` [RFC 0/3] How to pass IOMMU map attr via DMA API? Will Deacon
2013-06-20 9:59 ` Hiroshi Doyu
2013-06-20 10:11 ` Catalin Marinas
2013-06-20 11:00 ` Hiroshi Doyu
2013-06-20 10:12 ` Will Deacon
2013-06-21 7:17 ` Marek Szyprowski
2013-06-21 16:03 ` Joerg Roedel
2013-06-24 5:17 ` Hiroshi Doyu
2013-06-24 7:21 ` Joerg Roedel [this message]
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=20130624072128.GP11309@8bytes.org \
--to=joro@8bytes.org \
--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).