From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752403AbdF0IKi (ORCPT ); Tue, 27 Jun 2017 04:10:38 -0400 Received: from mx08-00178001.pphosted.com ([91.207.212.93]:41315 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751587AbdF0IK0 (ORCPT ); Tue, 27 Jun 2017 04:10:26 -0400 From: Pierre Yves MORDRET To: Rob Herring CC: Vinod Koul , Mark Rutland , Maxime Coquelin , Alexandre TORGUE , Russell King , Dan Williams , "M'boumba Cedric Madianga" , Fabrice GASNIER , Herbert Xu , Fabien DESSENNE , Amelie DELAUNAY , "dmaengine@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v2 3/5] dt-bindings: stm32-dma: Add property to handle STM32 DMAMUX Thread-Topic: [PATCH v2 3/5] dt-bindings: stm32-dma: Add property to handle STM32 DMAMUX Thread-Index: AQHS7CDNgCTCWPnwVE2dd1Ep9KlrEKI3bGaAgADTOwA= Date: Tue, 27 Jun 2017 08:09:35 +0000 Message-ID: References: <1498222853-11110-1-git-send-email-pierre-yves.mordret@st.com> <1498222853-11110-4-git-send-email-pierre-yves.mordret@st.com> <20170626193331.5jle4oxgvqmsvs5b@rob-hp-laptop> In-Reply-To: <20170626193331.5jle4oxgvqmsvs5b@rob-hp-laptop> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.75.127.51] Content-Type: text/plain; charset="utf-8" Content-ID: <0E476E8123F4AB4F94799C37693CB77A@st.com> MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-06-27_05:,, signatures=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id v5R8rbJZ009102 On 06/26/2017 09:33 PM, Rob Herring wrote: > On Fri, Jun 23, 2017 at 03:00:51PM +0200, Pierre-Yves MORDRET wrote: >> This patch adds an optional property needed for STM32 DMA controller >> addressed via STM32 DMAMUX. >> >> Signed-off-by: M'boumba Cedric Madianga >> Signed-off-by: Pierre-Yves MORDRET >> --- >> Version history: >> v2: >> * Typo fix >> --- >> --- >> Documentation/devicetree/bindings/dma/stm32-dma.txt | 5 ++++- >> 1 file changed, 4 insertions(+), 1 deletion(-) >> >> diff --git a/Documentation/devicetree/bindings/dma/stm32-dma.txt b/Documentation/devicetree/bindings/dma/stm32-dma.txt >> index 4408af6..340c918 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. > > Won't this be obvious looking at the bindings for clients? > > In any case, this should be implied by the compatible string. > > Rob > Not sure what you are asking here. Py From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Yves MORDRET Subject: Re: [PATCH v2 3/5] dt-bindings: stm32-dma: Add property to handle STM32 DMAMUX Date: Tue, 27 Jun 2017 08:09:35 +0000 Message-ID: References: <1498222853-11110-1-git-send-email-pierre-yves.mordret@st.com> <1498222853-11110-4-git-send-email-pierre-yves.mordret@st.com> <20170626193331.5jle4oxgvqmsvs5b@rob-hp-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20170626193331.5jle4oxgvqmsvs5b@rob-hp-laptop> Content-Language: en-US Content-ID: <0E476E8123F4AB4F94799C37693CB77A@st.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: Rob Herring Cc: Mark Rutland , "devicetree@vger.kernel.org" , Amelie DELAUNAY , Alexandre TORGUE , Vinod Koul , Russell King , Fabien DESSENNE , "linux-kernel@vger.kernel.org" , "dmaengine@vger.kernel.org" , Maxime Coquelin , M'boumba Cedric Madianga , Dan Williams , Fabrice GASNIER , "linux-arm-kernel@lists.infradead.org" , Herbert Xu List-Id: devicetree@vger.kernel.org On 06/26/2017 09:33 PM, Rob Herring wrote: > On Fri, Jun 23, 2017 at 03:00:51PM +0200, Pierre-Yves MORDRET wrote: >> This patch adds an optional property needed for STM32 DMA controller >> addressed via STM32 DMAMUX. >> >> Signed-off-by: M'boumba Cedric Madianga >> Signed-off-by: Pierre-Yves MORDRET >> --- >> Version history: >> v2: >> * Typo fix >> --- >> --- >> Documentation/devicetree/bindings/dma/stm32-dma.txt | 5 ++++- >> 1 file changed, 4 insertions(+), 1 deletion(-) >> >> diff --git a/Documentation/devicetree/bindings/dma/stm32-dma.txt b/Documentation/devicetree/bindings/dma/stm32-dma.txt >> index 4408af6..340c918 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. > > Won't this be obvious looking at the bindings for clients? > > In any case, this should be implied by the compatible string. > > Rob > Not sure what you are asking here. Py From mboxrd@z Thu Jan 1 00:00:00 1970 From: pierre-yves.mordret@st.com (Pierre Yves MORDRET) Date: Tue, 27 Jun 2017 08:09:35 +0000 Subject: [PATCH v2 3/5] dt-bindings: stm32-dma: Add property to handle STM32 DMAMUX In-Reply-To: <20170626193331.5jle4oxgvqmsvs5b@rob-hp-laptop> References: <1498222853-11110-1-git-send-email-pierre-yves.mordret@st.com> <1498222853-11110-4-git-send-email-pierre-yves.mordret@st.com> <20170626193331.5jle4oxgvqmsvs5b@rob-hp-laptop> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 06/26/2017 09:33 PM, Rob Herring wrote: > On Fri, Jun 23, 2017 at 03:00:51PM +0200, Pierre-Yves MORDRET wrote: >> This patch adds an optional property needed for STM32 DMA controller >> addressed via STM32 DMAMUX. >> >> Signed-off-by: M'boumba Cedric Madianga >> Signed-off-by: Pierre-Yves MORDRET >> --- >> Version history: >> v2: >> * Typo fix >> --- >> --- >> Documentation/devicetree/bindings/dma/stm32-dma.txt | 5 ++++- >> 1 file changed, 4 insertions(+), 1 deletion(-) >> >> diff --git a/Documentation/devicetree/bindings/dma/stm32-dma.txt b/Documentation/devicetree/bindings/dma/stm32-dma.txt >> index 4408af6..340c918 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. > > Won't this be obvious looking at the bindings for clients? > > In any case, this should be implied by the compatible string. > > Rob > Not sure what you are asking here. Py