Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-12-02 Thread Arnd Bergmann
On Wednesday 02 December 2015 10:22:09 Vinod Koul wrote: > > > > > > This legacy mode needs changes in platform code, in dmaengine drivers > > > > and > > > > finally the dmaengine user drivers can be converted: > > > > > > Are you marking the current APIs as dericated in the end of this series

Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-12-02 Thread Peter Ujfalusi
On 12/01/2015 04:24 PM, Arnd Bergmann wrote: > On Tuesday 01 December 2015 15:45:32 Peter Ujfalusi wrote: static struct dma_filter_map da830_edma_map[] = { DMA_FILTER_ENTRY("davinci-mcasp.0", "rx", EDMA_CTLR_CHAN(0, 0)), DMA_FILTER_ENTRY("davinci-mcasp.0", "tx",

Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-12-02 Thread Peter Ujfalusi
On 12/01/2015 10:17 PM, Arnd Bergmann wrote: > On Tuesday 01 December 2015 22:29:54 Vinod Koul wrote: >> On Mon, Nov 30, 2015 at 03:45:30PM +0200, Peter Ujfalusi wrote: >>> channel via DT, ACPI or in case if the kernel booted in non DT/ACPI mode >>> it will use a filter lookup table and retrieves

Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-12-02 Thread Arnd Bergmann
On Wednesday 02 December 2015 12:51:43 Peter Ujfalusi wrote: > On 12/01/2015 04:24 PM, Arnd Bergmann wrote: > > On Tuesday 01 December 2015 15:45:32 Peter Ujfalusi wrote: > static struct dma_filter_map da830_edma_map[] = { > DMA_FILTER_ENTRY("davinci-mcasp.0", "rx",

Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-12-01 Thread Arnd Bergmann
On Tuesday 01 December 2015 22:29:54 Vinod Koul wrote: > On Mon, Nov 30, 2015 at 03:45:30PM +0200, Peter Ujfalusi wrote: > > channel via DT, ACPI or in case if the kernel booted in non DT/ACPI mode > > it will use a filter lookup table and retrieves the needed information from > > the

Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-12-01 Thread Vinod Koul
On Mon, Nov 30, 2015 at 03:45:30PM +0200, Peter Ujfalusi wrote: > Hi, > > Changes since RFC v01: > - dma_request_chan(); lost the mask parameter > - The new API does not rely on RESOURCE_DMA, instead the dma_filter_map table > will be used to provide the needed information to the filter

Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-12-01 Thread Vinod Koul
On Tue, Dec 01, 2015 at 09:17:06PM +0100, Arnd Bergmann wrote: > On Tuesday 01 December 2015 22:29:54 Vinod Koul wrote: > > On Mon, Nov 30, 2015 at 03:45:30PM +0200, Peter Ujfalusi wrote: > > > channel via DT, ACPI or in case if the kernel booted in non DT/ACPI mode > > > it will use a filter

Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-12-01 Thread Peter Ujfalusi
On 11/30/2015 04:18 PM, Arnd Bergmann wrote: > On Monday 30 November 2015 15:45:30 Peter Ujfalusi wrote: >> Changes since RFC v01: >> - dma_request_chan(); lost the mask parameter >> - The new API does not rely on RESOURCE_DMA, instead the dma_filter_map table >> will be used to provide the

Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-12-01 Thread Arnd Bergmann
On Tuesday 01 December 2015 12:12:47 Peter Ujfalusi wrote: > > We would need: > { "da830-mmc.0", "rx", (void*)EDMA_CTLR_CHAN(0, 16) }, > { "da830-mmc.0", "tx", (void*)EDMA_CTLR_CHAN(0, 17) }, > > as we need to cast the param. > It is still compact, but having to add the (void*)

Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-12-01 Thread Peter Ujfalusi
On 11/30/2015 04:32 PM, Andy Shevchenko wrote: >> Andy: I did looked at the unified device properties, but I decided to not to >> use >> it as I don't see it to fit well and most of the legacy board files are using >> resources to specify at least their memory regions so adding the DMA resource

Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-12-01 Thread Arnd Bergmann
On Tuesday 01 December 2015 15:45:32 Peter Ujfalusi wrote: > >> static struct dma_filter_map da830_edma_map[] = { > >> DMA_FILTER_ENTRY("davinci-mcasp.0", "rx", EDMA_CTLR_CHAN(0, 0)), > >> DMA_FILTER_ENTRY("davinci-mcasp.0", "tx", EDMA_CTLR_CHAN(0, 1)), > >>

[RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-11-30 Thread Peter Ujfalusi
Hi, Changes since RFC v01: - dma_request_chan(); lost the mask parameter - The new API does not rely on RESOURCE_DMA, instead the dma_filter_map table will be used to provide the needed information to the filter function in legacy mode - Extended the example patches to convert most of daVinci

Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-11-30 Thread Arnd Bergmann
On Monday 30 November 2015 15:45:30 Peter Ujfalusi wrote: > Changes since RFC v01: >- dma_request_chan(); lost the mask parameter >- The new API does not rely on RESOURCE_DMA, instead the dma_filter_map table > will be used to provide the needed information to the filter function in > legacy

Re: [RFC v02 00/15] dmaengine: New 'universal' API for requesting channel

2015-11-30 Thread Andy Shevchenko
On Mon, Nov 30, 2015 at 3:45 PM, Peter Ujfalusi wrote: > Hi, > > Changes since RFC v01: > - dma_request_chan(); lost the mask parameter > - The new API does not rely on RESOURCE_DMA, instead the dma_filter_map table > will be used to provide the needed information to the