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 not specify a version for individual IP blocks. For these > reasons a convention of using the SoC name in place of a version and > providing SoC-specific compat strings has been adopted. Everyone learns this the hard way. :) > Although not universally liked this convention is used in the bindings for > most drivers for Renesas hardware. The purpose of this patch is to > update the Renesas R-Car DMA Controller driver to follow this convention. > > Cc: devicetree@xxxxxxxxxxxxxxx > Cc: Magnus Damm <magnus.damm@xxxxxxxxx> > Cc: Laurent Pinchart <laurent.pinchart+renesas@xxxxxxxxxxxxxxxx> > Signed-off-by: Simon Horman <horms+renesas@xxxxxxxxxxxx> > --- > Documentation/devicetree/bindings/dma/renesas,rcar-dmac.txt | 13 ++++++++++--- > 1 file changed, 10 insertions(+), 3 deletions(-) > > Once this has been merged I intend to provide follow-up patches > to use these new compat strings in the relevant dtsi files. > > 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/renesas,rcar-dmac.txt > +++ b/Documentation/devicetree/bindings/dma/renesas,rcar-dmac.txt > @@ -14,7 +14,14 @@ not described in these device tree bindings. > > Required Properties: > > -- compatible: must contain "renesas,rcar-dmac" > +- compatible: "renesas,dmac-<soctype>", "renesas,rcar-dmac" as fallback. Somehow Renesas has ended up being backwards from everyone else that does <vendor>,<chip>-<block>. Oh well... Acked-by: Rob Herring <robh@xxxxxxxxxx> Rob -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html