[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170706141045.GA577@lst.de>
Date: Thu, 6 Jul 2017 16:10:45 +0200
From: Christoph Hellwig <hch@....de>
To: Robin Murphy <robin.murphy@....com>
Cc: Tomasz Figa <tfiga@...omium.org>,
"open list:IOMMU DRIVERS" <iommu@...ts.linux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@....de>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Joerg Roedel <joro@...tes.org>,
Will Deacon <will.deacon@....com>,
Vineet Gupta <vgupta@...opsys.com>,
Hans-Christian Noren Egtvedt <egtvedt@...fundet.no>,
Mitchel Humpherys <mitchelh@...eaurora.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [RFC PATCH 4/5] iommu/dma: Export non-static functions to use
in modules
On Thu, Jul 06, 2017 at 12:09:45PM +0100, Robin Murphy wrote:
> I suppose another option is to just make the IOMMU and DMA ops a
> self-contained non-modular driver mirroring the VT-d/AMD-Vi IOMMUs -
> AFAICS it shouldn't have to be all that tightly coupled to the IPU bus
> code, the latter more or less just needs to create the appropriate IOMMU
> device for the driver to find.
I still haven't seen the driver code, but this seems to be best
solution so far. Given that it's not a plug in device but part of
an SOC that seems perfectly acceptable to me.
Powered by blists - more mailing lists