[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <91ef4036-6468-4ecc-ac14-0146130d8da4@arm.com>
Date: Tue, 27 Aug 2024 13:31:59 +0100
From: Robin Murphy <robin.murphy@....com>
To: Christoph Hellwig <hch@....de>, iommu@...ts.linux.dev
Cc: Marek Szyprowski <m.szyprowski@...sung.com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Bingbu Cao <bingbu.cao@...el.com>, "Michael S . Tsirkin" <mst@...hat.com>,
Jason Wang <jasowang@...hat.com>, linux-kernel@...r.kernel.org,
linux-alpha@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mips@...r.kernel.org, linux-parisc@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-s390@...r.kernel.org,
sparclinux@...r.kernel.org, linux-media@...r.kernel.org,
virtualization@...ts.linux.dev, xen-devel@...ts.xenproject.org
Subject: Re: [PATCH] dma-mapping: clear mark DMA ops as an architecture
feature
On 24/08/2024 4:57 am, Christoph Hellwig wrote:
> DMA ops are a helper for architectures and not for drivers to override
> the DMA implementation. Unfortunately driver authors keep ignoring
> this. Make this more clear by renaming the symbol to ARCH_DMA_OPS,
> have the three drivers overriding it depend on that. They should
> probably also be marked broken, but we can give them a bit of a grace
> period for that.
Nit: from a quick survey of "git grep 'select ARCH_'", maybe
ARCH_HAS_DMA_OPS might be the clearest and most consistent name?
Otherwise, now that any potential confusion from drivers/iommu is no
more, I too thoroughly approve of the overall idea.
Acked-by: Robin Murphy <robin.murphy@....com>
Powered by blists - more mailing lists