[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56331A45.6020201@ti.com>
Date: Fri, 30 Oct 2015 09:20:37 +0200
From: Peter Ujfalusi <peter.ujfalusi@...com>
To: <vinod.koul@...el.com>, <nsekhar@...com>
CC: <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-omap@...r.kernel.org>,
<dmaengine@...r.kernel.org>, <devicetree@...r.kernel.org>,
<tony@...mide.com>, <r.schwebel@...gutronix.de>
Subject: Re: [PATCH 0/3] dmaengine: ti-dma-crossbar: channel reserving and
edma3-tcc support
Vinod,
On 10/29/2015 10:28 AM, Peter Ujfalusi wrote:
> Hi,
>
> This series depends on the eDMA work I have done, which has been now applied:
> https://lkml.org/lkml/2015/10/16/64
>
> DRA7 family of chips have both sDMA and eDMA. Currently only sDMA can be used
> becasue the old driver stack for eDMA did not allowed integration w/o hacks.
>
> Due to the nature of eDMA the crossbar needs to know which eDMA events it can
> use to map incoming events towards the eDMA. In eDMA a channel is wired to be
> used with one specific event. For example eDMA event 14 can only be handled by
> eDMA channel 14.
> The eDMA itself can be shared by different processors in the system (ARM, DSP,
> etc) and since ARM/Linux is the master we need to know which channels are used
> by other cores. Also we need to mask out channels used for memcpy from the
> events we use for HW triggers.
Please ignore this series, I have found some issue with it and I just started
to debug it. Will post V2 as soon as I found the problem.
>
> Regards,
> Peter
> ---
> Peter Ujfalusi (3):
> dmaengine: ti-dma-crossbar: dra7: Use bitops instead of idr
> dmaengine: ti-dma-crossbar: dra7: Support for reserving DMA event
> ranges
> dmaengine: ti-dma-crossbar: dra7: Support for eDMA with new bindings
>
> .../devicetree/bindings/dma/ti-dma-crossbar.txt | 6 ++
> drivers/dma/ti-dma-crossbar.c | 81 +++++++++++++++++++---
> 2 files changed, 76 insertions(+), 11 deletions(-)
>
--
Péter
--
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