Thread (58 messages) 58 messages, 10 authors, 2015-11-20

Re: [PATCH 02/13] dmaengine: Introduce dma_request_slave_channel_compat_reason()

From: Vinod Koul <hidden>
Date: 2015-11-18 16:03:34
Also in: alsa-devel, linux-crypto, linux-media, linux-mmc, linux-omap, linux-serial, linux-spi, lkml

On Wed, Nov 18, 2015 at 04:51:54PM +0100, Arnd Bergmann wrote:
On Wednesday 18 November 2015 17:43:04 Andy Shevchenko wrote:
quoted
quoted
I assume that the sst-firmware.c case is a mistake, it should just use a
plain DMA_SLAVE and not DMA_MEMCPY.
Other way around.
Ok, I see. In that case I guess it also shouldn't call
dmaengine_slave_config(), right? I don't think that's valid
on a MEMCPY channel.
Yes it is not valid. In this case the dma driver should invoke a generic memcpy
and not need slave parameters, knowing the hw and reason for this (firmware
download to DSP memory), this doesn't qualify for slave case.
In fact filter function doesn't need a channel, any channel in this
controller will be good

-- 
~Vinod
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help