[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120917083654.GO12245@n2100.arm.linux.org.uk>
Date: Mon, 17 Sep 2012 09:36:54 +0100
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Vinod Koul <vinod.koul@...ux.intel.com>
Cc: linux-kernel@...r.kernel.org, Dan Williams <djbw@...com>,
Arnd Bergmann <arnd@...db.de>, linus.walleij@...aro.org,
Jon Hunter <jon-hunter@...com>,
Stephen Warren <swarren@...dia.com>,
Benoit Cousson <b-cousson@...com>,
Shawn Guo <shawn.guo@...aro.org>,
Guennadi Liakhovetski <g.liakhovetski@....de>,
Sascha Hauer <kernel@...gutronix.de>,
Kukjin Kim <kgene.kim@...sung.com>,
viresh kumar <viresh.kumar@...aro.org>,
Paul Mundt <lethal@...ux-sh.org>
Subject: Re: [PATCH] dmaengine: add dmanegine slave map api's
On Mon, Sep 17, 2012 at 09:10:23AM +0530, Vinod Koul wrote:
> On Fri, 2012-09-14 at 12:18 +0100, Russell King - ARM Linux wrote:
> > I'm not saying take the slave_id out of the map. I'm saying, let the
> > DMA engine driver itself figure out what dma_chan to return.
> But wont that assume the dma controller knows which channel to allocate.
> And how would it know this information? This can be problematic for hard
> wired muxes, but can be easily done for controller which have
> programmable mux.
Well, as I have already said, at the moment you're returning the _first_
_free_ _channel_ on a DMA device, which almost certainly will always be
the wrong one.
--
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