Re: [PATCH] dmaengine: Stricter legacy checking in dma_request_slave_channel_compat()

2015-08-20 Thread Vinod Koul
On Mon, Aug 17, 2015 at 03:08:55PM +0200, Geert Uytterhoeven wrote: > dma_request_slave_channel_compat() is meant for drivers that support > both DT and legacy platform device based probing: if DT channel DMA > setup fails, it will fall back to platform data based DMA channel setup, > using

Re: [PATCH] dmaengine: Stricter legacy checking in dma_request_slave_channel_compat()

2015-08-20 Thread Vinod Koul
On Mon, Aug 17, 2015 at 03:08:55PM +0200, Geert Uytterhoeven wrote: dma_request_slave_channel_compat() is meant for drivers that support both DT and legacy platform device based probing: if DT channel DMA setup fails, it will fall back to platform data based DMA channel setup, using hardcoded

[PATCH] dmaengine: Stricter legacy checking in dma_request_slave_channel_compat()

2015-08-17 Thread Geert Uytterhoeven
dma_request_slave_channel_compat() is meant for drivers that support both DT and legacy platform device based probing: if DT channel DMA setup fails, it will fall back to platform data based DMA channel setup, using hardcoded DMA channel IDs and a filter function. However, if the DTS doesn't

[PATCH] dmaengine: Stricter legacy checking in dma_request_slave_channel_compat()

2015-08-17 Thread Geert Uytterhoeven
dma_request_slave_channel_compat() is meant for drivers that support both DT and legacy platform device based probing: if DT channel DMA setup fails, it will fall back to platform data based DMA channel setup, using hardcoded DMA channel IDs and a filter function. However, if the DTS doesn't