From: Robin Murphy <robin.murphy@arm.com>
To: Christoph Hellwig <hch@infradead.org>, Rob Herring <robh@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will.deacon@arm.com>,
iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] iommu: Allow io-pgtable to be used outside of drivers/iommu/
Date: Tue, 5 Feb 2019 17:12:29 +0000 [thread overview]
Message-ID: <a6002b86-e18a-dd97-6dad-ab69e994678d@arm.com> (raw)
In-Reply-To: <20190205165528.GA20157@infradead.org>
On 05/02/2019 16:55, Christoph Hellwig wrote:
> On Tue, Feb 05, 2019 at 10:37:31AM -0600, Rob Herring wrote:
>> Move io-pgtable.h to include/linux/ and export alloc_io_pgtable_ops
>> and free_io_pgtable_ops. This enables drivers outside drivers/iommu/ to
>> use the ARM page table library. Specifically, some ARM Mali GPUs use the
>> ARM page table formats.
>
> Maybe rename it to arm-io-pgtable.h to make the usage a little more
> clear?
It's not Arm-specific, though - the whole point of io-pgtable is to be
an architecture-agnostic library of IOMMU pagetable code. It just
happens that the only formats implemented so far are the Arm ones that
already have more than one in-tree user each.
Robin.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-05 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 16:37 [PATCH] iommu: Allow io-pgtable to be used outside of drivers/iommu/ Rob Herring
2019-02-05 16:55 ` Christoph Hellwig
2019-02-05 17:12 ` Robin Murphy [this message]
2019-02-06 6:55 ` Christoph Hellwig
2019-02-05 17:20 ` Rob Herring
2019-02-11 10:27 ` 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=a6002b86-e18a-dd97-6dad-ab69e994678d@arm.com \
--to=robin.murphy@arm.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=will.deacon@arm.com \
/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).