Messages in this thread | | | Date | Mon, 26 Jun 2017 14:33:31 -0500 | From | Rob Herring <> | Subject | Re: [PATCH v2 3/5] dt-bindings: stm32-dma: Add property to handle STM32 DMAMUX |
| |
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 <cedric.madianga@gmail.com> > Signed-off-by: Pierre-Yves MORDRET <pierre-yves.mordret@st.com> > --- > 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
| |