[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130806101914.GH23053@n2100.arm.linux.org.uk>
Date: Tue, 6 Aug 2013 11:19:14 +0100
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Pantelis Antoniou <panto@...oniou-consulting.com>,
Tony Lindgren <tony@...mide.com>,
BenoƮt Coussno <b-cousson@...com>,
Paul Walmsley <paul@...an.com>,
Sourav Poddar <sourav.poddar@...com>,
Russ Dill <Russ.Dill@...com>, Felipe Balbi <balbi@...com>,
Koen Kooi <koen@...cuitco.com>, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/5] pdev: Fix platform device resource linking
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists