[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170616084701.GE10582@lst.de>
Date: Fri, 16 Jun 2017 10:47:01 +0200
From: Christoph Hellwig <hch@....de>
To: Julian Calaby <julian.calaby@...il.com>
Cc: Christoph Hellwig <hch@....de>, x86@...nel.org,
"Mailing List, Arm" <linux-arm-kernel@...ts.infradead.org>,
xen-devel@...ts.xenproject.org, linux-c6x-dev@...ux-c6x.org,
linux-hexagon@...r.kernel.org, linux-ia64@...r.kernel.org,
linux-mips@...ux-mips.org, openrisc@...ts.librecores.org,
linuxppc-dev@...ts.ozlabs.org, linux-s390@...r.kernel.org,
linux-sh@...r.kernel.org, sparclinux <sparclinux@...r.kernel.org>,
linux-xtensa@...ux-xtensa.org, dmaengine@...r.kernel.org,
linux-tegra@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-samsung-soc@...r.kernel.org,
iommu@...ts.linux-foundation.org, netdev <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 28/44] sparc: remove arch specific dma_supported
implementations
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.
Powered by blists - more mailing lists