Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756189Ab3HGI1r (ORCPT ); Wed, 7 Aug 2013 04:27:47 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:40659 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755676Ab3HGI1q (ORCPT ); Wed, 7 Aug 2013 04:27:46 -0400 Date: Wed, 7 Aug 2013 09:27:24 +0100 From: Russell King - ARM Linux To: Greg Kroah-Hartman Cc: Pantelis Antoniou , Tony Lindgren , =?iso-8859-1?Q?Beno=EEt?= Coussno , Paul Walmsley , Sourav Poddar , Russ Dill , Felipe Balbi , Koen Kooi , linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/5] pdev: Fix platform device resource linking Message-ID: <20130807082723.GI23053@n2100.arm.linux.org.uk> References: <1375775624-12250-1-git-send-email-panto@antoniou-consulting.com> <1375775624-12250-2-git-send-email-panto@antoniou-consulting.com> <20130806093601.GB27889@kroah.com> <311C42C3-6544-4058-ABE9-F9FAE72DD5CA@antoniou-consulting.com> <20130806101527.GB29283@kroah.com> <20130806101914.GH23053@n2100.arm.linux.org.uk> <20130807055700.GD5304@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130807055700.GD5304@kroah.com> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1406 Lines: 28 On Wed, Aug 07, 2013 at 02:57:00PM +0900, Greg Kroah-Hartman wrote: > On Tue, Aug 06, 2013 at 11:19:14AM +0100, Russell King - ARM Linux wrote: > > On Tue, Aug 06, 2013 at 06:15:27PM +0800, Greg Kroah-Hartman wrote: > > > On Tue, Aug 06, 2013 at 12:45:42PM +0300, Pantelis Antoniou wrote: > > > > What would it take to move all this into driver core? > > > > > > What specifically would you move into there? > > > > A variable to hold the streaming dma_mask, so that its in struct device > > rather than having to be separate. Yes, we can keep the pointer in there > > too, because that appears to convey meaning in the kernel today - whether > > the device can do DMA or not. > > > > A NULL dma_mask pointer already means it can't and dma_set_mask() always > > fails. A non-NULL dma_mask pointer means the driver can use > > dma_set_mask() to set an appropriate mask. > > Ok, that sounds fine to me, for some reason I thought I said yes to this > a long time ago, did no one ever send me a patch for it? Apparantly not. I'll see what I can do, and I'll add it to my dma-masks series, probably below most of the existing patches that are already there. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/