[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH 28/44] sparc: remove arch specific dma_supported implementations
- To: Julian Calaby <julian.calaby@xxxxxxxxx>
- From: Christoph Hellwig <hch@xxxxxx>
- Date: Fri, 16 Jun 2017 10:47:01 +0200
- Cc: linux-mips@xxxxxxxxxxxxxx, linux-samsung-soc@xxxxxxxxxxxxxxx, linux-ia64@xxxxxxxxxxxxxxx, linux-c6x-dev@xxxxxxxxxxxxx, linux-s390@xxxxxxxxxxxxxxx, linux-sh@xxxxxxxxxxxxxxx, linux-hexagon@xxxxxxxxxxxxxxx, linux-xtensa@xxxxxxxxxxxxxxxx, x86@xxxxxxxxxx, linux-tegra@xxxxxxxxxxxxxxx, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, dri-devel@xxxxxxxxxxxxxxxxxxxxx, dmaengine@xxxxxxxxxxxxxxx, iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx, openrisc@xxxxxxxxxxxxxxxxxxxx, netdev <netdev@xxxxxxxxxxxxxxx>, sparclinux <sparclinux@xxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, linuxppc-dev@xxxxxxxxxxxxxxxx, Christoph Hellwig <hch@xxxxxx>, "Mailing List, Arm" <linux-arm-kernel@xxxxxxxxxxxxxxxxxxx>
- Delivery-date: Fri, 16 Jun 2017 08:47:12 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On Fri, Jun 09, 2017 at 12:22:48AM +1000, Julian Calaby wrote:
> I'm guessing there's a few places that have DMA ops but DMA isn't
> actually supported. Why not have a common method for this, maybe
> "dma_not_supported"?
It's not common at all. Except for sbus all dma API user first
call set_dma_mask which ends up in the dma_supported call. sbus
is the weird outlier here.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel
|
