Re: [PATCH] dmaengine: rcar-dmac: Document SoC specific bindings

2015-11-15 Thread Vinod Koul
On Thu, Nov 12, 2015 at 10:53:59AM +0900, Simon Horman wrote: > In general Renesas hardware is not documented to the extent where the > relationship between IP blocks on different SoCs can be assumed although > they may appear to operate the same way. Furthermore the documentation > typically does

Re: [PATCH] dmaengine: rcar-dmac: Document SoC specific bindings

2015-11-13 Thread Geert Uytterhoeven
Hi Rob, On Fri, Nov 13, 2015 at 12:28 AM, Rob Herring wrote: >> diff --git a/Documentation/devicetree/bindings/dma/renesas,rcar-dmac.txt >> b/Documentation/devicetree/bindings/dma/renesas,rcar-dmac.txt >> index 09daeef1ff22..5b902ac8d97e 100644 >> --- a/Documentation/devicetree/bindings/dma/rene

Re: [PATCH] dmaengine: rcar-dmac: Document SoC specific bindings

2015-11-12 Thread Rob Herring
On Thu, Nov 12, 2015 at 10:53:59AM +0900, Simon Horman wrote: > In general Renesas hardware is not documented to the extent where the > relationship between IP blocks on different SoCs can be assumed although > they may appear to operate the same way. Furthermore the documentation > typically does

Re: [PATCH] dmaengine: rcar-dmac: Document SoC specific bindings

2015-11-12 Thread Geert Uytterhoeven
Hi Simon, On Thu, Nov 12, 2015 at 2:53 AM, Simon Horman wrote: > In general Renesas hardware is not documented to the extent where the > relationship between IP blocks on different SoCs can be assumed although > they may appear to operate the same way. Furthermore the documentation > typically do

[PATCH] dmaengine: rcar-dmac: Document SoC specific bindings

2015-11-11 Thread Simon Horman
In general Renesas hardware is not documented to the extent where the relationship between IP blocks on different SoCs can be assumed although they may appear to operate the same way. Furthermore the documentation typically does not specify a version for individual IP blocks. For these reasons a co