From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 0/3] How to pass IOMMU map attr via DMA API?
Date: Thu, 20 Jun 2013 11:12:22 +0100 [thread overview]
Message-ID: <20130620101222.GF2842@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20130620.125929.2250094502232662356.hdoyu@nvidia.com>
On Thu, Jun 20, 2013 at 10:59:29AM +0100, Hiroshi Doyu wrote:
> Hi Will,
Hi Hiroshi,
> Will Deacon <will.deacon@arm.com> wrote @ Thu, 20 Jun 2013 11:31:52 +0200:
>
> > > Hiroshi Doyu (3):
> > > common: DMA-mapping: add DMA_ATTR_READ_ONLY attribute
> > > ARM: dma-mapping: Pass DMA attrs as IOMMU prot
> > > iommu/tegra: smmu: Support read-only mapping
> >
> > These patches don't seem to have made it to the linux-arm-kernel list
> > (either in my inbox or the list archive). Could you try and resend them please?
>
> I'm sorry but linux-arm-kernel list someitmes requires me moderators
> approval. I don't know why. I'll find a way to work around.
Strange. It would definitely be good to get that fixed!
> Here are links for the original post:
>
> http://lists.linuxfoundation.org/pipermail/iommu/2013-June/005860.html
> http://lists.linuxfoundation.org/pipermail/iommu/2013-June/005861.html
> http://lists.linuxfoundation.org/pipermail/iommu/2013-June/005862.html
> http://lists.linuxfoundation.org/pipermail/iommu/2013-June/005863.html
Thanks, but I can't reply inline to those :)
> > Also: how do they interact with my patch here?:
> >
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2013-June/175124.html
>
> This conversion looks reasonable enough, but some platform may need
> more attrs to pass IOMMU like OMAP.
>
> #define IOMMU_FLAG (IOVMF_ENDIAN_LITTLE | IOVMF_ELSZ_8)
>
> How can we deal with those cases?
Well, if we have weird and wonderful flags like this, which are
IOMMU-specific, then I'd suggest short-circuiting the flags altogether and
putting them inside somewhere like dev_archdata.iommu.
Will
next prev parent reply other threads:[~2013-06-20 10:12 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 [this message]
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
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=20130620101222.GF2842@mudshark.cambridge.arm.com \
--to=will.deacon@arm.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 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).