Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031830AbbKFVxR (ORCPT ); Fri, 6 Nov 2015 16:53:17 -0500 Received: from mail.kernel.org ([198.145.29.136]:48188 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966102AbbKFVxP (ORCPT ); Fri, 6 Nov 2015 16:53:15 -0500 Date: Fri, 6 Nov 2015 15:53:10 -0600 From: Rob Herring To: Peter Ujfalusi Cc: vinod.koul@intel.com, nsekhar@ti.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, dmaengine@vger.kernel.org, devicetree@vger.kernel.org, tony@atomide.com, r.schwebel@pengutronix.de Subject: Re: [PATCH v2 2/3] dmaengine: ti-dma-crossbar: dra7: Support for reserving DMA event ranges Message-ID: <20151106215310.GA20278@rob-hp-laptop> References: <1446192038-11158-1-git-send-email-peter.ujfalusi@ti.com> <1446192038-11158-3-git-send-email-peter.ujfalusi@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1446192038-11158-3-git-send-email-peter.ujfalusi@ti.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1828 Lines: 36 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 event number already allocated in eDMA for memcpy. Furthermore the > eDMA can be shared with DSP in which case the crossbar driver should also > avoid mapping xbar events to DSP used event numbers (or channels). > > Signed-off-by: Peter Ujfalusi > --- > .../devicetree/bindings/dma/ti-dma-crossbar.txt | 6 +++ > drivers/dma/ti-dma-crossbar.c | 47 ++++++++++++++++++++-- > 2 files changed, 49 insertions(+), 4 deletions(-) > > diff --git a/Documentation/devicetree/bindings/dma/ti-dma-crossbar.txt b/Documentation/devicetree/bindings/dma/ti-dma-crossbar.txt > index b152a75dceae..aead5869a28d 100644 > --- a/Documentation/devicetree/bindings/dma/ti-dma-crossbar.txt > +++ b/Documentation/devicetree/bindings/dma/ti-dma-crossbar.txt > @@ -14,6 +14,10 @@ The DMA controller node need to have the following poroperties: > > Optional properties: > - ti,dma-safe-map: Safe routing value for unused request lines > +- ti,reserved-dma-request-ranges: DMA request ranges which should not be used > + when mapping xbar input to DMA request, they are either > + allocated to be used by for example the DSP or they are used as > + memcpy channels in eDMA. How many requests are there? I think I'd rather see this as a mask value. Rob -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/