From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755973AbdCTVqS (ORCPT ); Mon, 20 Mar 2017 17:46:18 -0400 Received: from mail-ot0-f196.google.com ([74.125.82.196]:34034 "EHLO mail-ot0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753165AbdCTVqQ (ORCPT ); Mon, 20 Mar 2017 17:46:16 -0400 Date: Mon, 20 Mar 2017 16:37:22 -0500 From: Rob Herring To: "M'boumba Cedric Madianga" Cc: vinod.koul@intel.com, mark.rutland@arm.com, mcoquelin.stm32@gmail.com, alexandre.torgue@st.com, dan.j.williams@intel.com, dmaengine@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 3/5] dt-bindings: stm32-dma: Add property to handle STM32 DMAMUX Message-ID: <20170320213722.oj3ipmslbw2mp27d@rob-hp-laptop> References: <1489414561-28912-1-git-send-email-cedric.madianga@gmail.com> <1489414561-28912-4-git-send-email-cedric.madianga@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1489414561-28912-4-git-send-email-cedric.madianga@gmail.com> User-Agent: Mutt/1.6.2-neo (2016-08-21) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 13, 2017 at 03:15:59PM +0100, M'boumba Cedric Madianga wrote: > This patch adds an optional property needed for STM32 DMA controller > addressed via STM32 DMAMUX. > > Signed-off-by: M'boumba Cedric Madianga > --- > Documentation/devicetree/bindings/dma/stm32-dma.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/dma/stm32-dma.txt b/Documentation/devicetree/bindings/dma/stm32-dma.txt > index 4408af6..7b5e91a 100644 > --- a/Documentation/devicetree/bindings/dma/stm32-dma.txt > +++ b/Documentation/devicetree/bindings/dma/stm32-dma.txt > @@ -16,6 +16,9 @@ Optional properties: > - resets: Reference to a reset controller asserting the DMA controller > - st,mem2mem: boolean; if defined, it indicates that the controller supports > memory-to-memory transfer > +- st,dmamux: boolean; if defined, it indicates that the controller is behind a > + DMA multiplexer. In that case, using dma instances doesn't work for DMA > + clients. They have to use dma-router instances. This should not be needed for the same reason we don't need anything like this for chained interrupt controllers. Also, the compatible string should be specific enough to provide this information. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH 3/5] dt-bindings: stm32-dma: Add property to handle STM32 DMAMUX Date: Mon, 20 Mar 2017 16:37:22 -0500 Message-ID: <20170320213722.oj3ipmslbw2mp27d@rob-hp-laptop> References: <1489414561-28912-1-git-send-email-cedric.madianga@gmail.com> <1489414561-28912-4-git-send-email-cedric.madianga@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1489414561-28912-4-git-send-email-cedric.madianga@gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: M'boumba Cedric Madianga Cc: mark.rutland@arm.com, devicetree@vger.kernel.org, alexandre.torgue@st.com, vinod.koul@intel.com, linux-kernel@vger.kernel.org, mcoquelin.stm32@gmail.com, dmaengine@vger.kernel.org, dan.j.williams@intel.com, linux-arm-kernel@lists.infradead.org List-Id: devicetree@vger.kernel.org On Mon, Mar 13, 2017 at 03:15:59PM +0100, M'boumba Cedric Madianga wrote: > This patch adds an optional property needed for STM32 DMA controller > addressed via STM32 DMAMUX. > > Signed-off-by: M'boumba Cedric Madianga > --- > Documentation/devicetree/bindings/dma/stm32-dma.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/dma/stm32-dma.txt b/Documentation/devicetree/bindings/dma/stm32-dma.txt > index 4408af6..7b5e91a 100644 > --- a/Documentation/devicetree/bindings/dma/stm32-dma.txt > +++ b/Documentation/devicetree/bindings/dma/stm32-dma.txt > @@ -16,6 +16,9 @@ Optional properties: > - resets: Reference to a reset controller asserting the DMA controller > - st,mem2mem: boolean; if defined, it indicates that the controller supports > memory-to-memory transfer > +- st,dmamux: boolean; if defined, it indicates that the controller is behind a > + DMA multiplexer. In that case, using dma instances doesn't work for DMA > + clients. They have to use dma-router instances. This should not be needed for the same reason we don't need anything like this for chained interrupt controllers. Also, the compatible string should be specific enough to provide this information. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 From: robh@kernel.org (Rob Herring) Date: Mon, 20 Mar 2017 16:37:22 -0500 Subject: [PATCH 3/5] dt-bindings: stm32-dma: Add property to handle STM32 DMAMUX In-Reply-To: <1489414561-28912-4-git-send-email-cedric.madianga@gmail.com> References: <1489414561-28912-1-git-send-email-cedric.madianga@gmail.com> <1489414561-28912-4-git-send-email-cedric.madianga@gmail.com> Message-ID: <20170320213722.oj3ipmslbw2mp27d@rob-hp-laptop> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Mar 13, 2017 at 03:15:59PM +0100, M'boumba Cedric Madianga wrote: > This patch adds an optional property needed for STM32 DMA controller > addressed via STM32 DMAMUX. > > Signed-off-by: M'boumba Cedric Madianga > --- > Documentation/devicetree/bindings/dma/stm32-dma.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/dma/stm32-dma.txt b/Documentation/devicetree/bindings/dma/stm32-dma.txt > index 4408af6..7b5e91a 100644 > --- a/Documentation/devicetree/bindings/dma/stm32-dma.txt > +++ b/Documentation/devicetree/bindings/dma/stm32-dma.txt > @@ -16,6 +16,9 @@ Optional properties: > - resets: Reference to a reset controller asserting the DMA controller > - st,mem2mem: boolean; if defined, it indicates that the controller supports > memory-to-memory transfer > +- st,dmamux: boolean; if defined, it indicates that the controller is behind a > + DMA multiplexer. In that case, using dma instances doesn't work for DMA > + clients. They have to use dma-router instances. This should not be needed for the same reason we don't need anything like this for chained interrupt controllers. Also, the compatible string should be specific enough to provide this information. Rob