Re: [PATCH v2 2/3] dmaengine: ti-dma-crossbar: dra7: Support for reserving DMA event ranges

2015-11-09 Thread Peter Ujfalusi
On 11/06/2015 11:53 PM, Rob Herring wrote: > On Fri, Oct 30, 2015 at 10:00:37AM +0200, Peter Ujfalusi wrote: >> In eDMA the events are directly mapped to a DMA channel (for example DMA >> event 14 can only be handled by DMA channel 14). If the memcpy is enabled >> on the eDMA, there is a possibilit

Re: [PATCH v2 2/3] dmaengine: ti-dma-crossbar: dra7: Support for reserving DMA event ranges

2015-11-06 Thread Rob Herring
On Fri, Oct 30, 2015 at 10:00:37AM +0200, Peter Ujfalusi wrote: > In eDMA the events are directly mapped to a DMA channel (for example DMA > event 14 can only be handled by DMA channel 14). If the memcpy is enabled > on the eDMA, there is a possibility that the crossbar driver would assign > DMA ev

[PATCH v2 2/3] dmaengine: ti-dma-crossbar: dra7: Support for reserving DMA event ranges

2015-10-30 Thread Peter Ujfalusi
In eDMA the events are directly mapped to a DMA channel (for example DMA event 14 can only be handled by DMA channel 14). If the memcpy is enabled on the eDMA, there is a possibility that the crossbar driver would assign DMA event number already allocated in eDMA for memcpy. Furthermore the eDMA ca