Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753185AbdFPIrH (ORCPT ); Fri, 16 Jun 2017 04:47:07 -0400 Received: from verein.lst.de ([213.95.11.211]:42959 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752067AbdFPIrE (ORCPT ); Fri, 16 Jun 2017 04:47:04 -0400 Date: Fri, 16 Jun 2017 10:47:01 +0200 From: Christoph Hellwig To: Julian Calaby Cc: Christoph Hellwig , x86@kernel.org, "Mailing List, Arm" , xen-devel@lists.xenproject.org, linux-c6x-dev@linux-c6x.org, linux-hexagon@vger.kernel.org, linux-ia64@vger.kernel.org, linux-mips@linux-mips.org, openrisc@lists.librecores.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux , linux-xtensa@linux-xtensa.org, dmaengine@vger.kernel.org, linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-samsung-soc@vger.kernel.org, iommu@lists.linux-foundation.org, netdev , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 28/44] sparc: remove arch specific dma_supported implementations Message-ID: <20170616084701.GE10582@lst.de> References: <20170608132609.32662-1-hch@lst.de> <20170608132609.32662-29-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 378 Lines: 8 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.