> -----Original Message----- > From: linux-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:linux-devel- > bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Bhaskar Upadhaya > Sent: Friday, August 26, 2016 5:28 AM > To: devicetree@xxxxxxxxxxxxxxx; shawnguo@xxxxxxxxxx > Cc: oss@xxxxxxxxxxxx; linux-devel@xxxxxxxxxxxxxxxxxxxx; Bhaskar U > <bhaskar.upadhaya@xxxxxxx>; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > Subject: [linux-devel] [PATCH 02/10] dt-bindings: esdhc: Update bindings for > LS1012A > > Signed-off-by: Bhaskar Upadhaya <Bhaskar.Upadhaya@xxxxxxx> > --- > Documentation/devicetree/bindings/mmc/fsl-esdhc.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/mmc/fsl-esdhc.txt > b/Documentation/devicetree/bindings/mmc/fsl-esdhc.txt > index dedfb02..3257b4a 100644 > --- a/Documentation/devicetree/bindings/mmc/fsl-esdhc.txt > +++ b/Documentation/devicetree/bindings/mmc/fsl-esdhc.txt > @@ -7,9 +7,9 @@ This file documents differences between the core properties > described by mmc.txt and the properties used by the sdhci-esdhc driver. > > Required properties: > + - compatible : "fsl,mpc8378-esdhc", "fsl,ls1012a-esdhc0", "fsl,ls1012a- > esdhc1". What does it mean for esdhc0 and esdhc1? If these are two different controllers used on the same chip, please describe what is the difference. It is not clear from the name itself. > - interrupt-parent : interrupt source phandle. > - clock-frequency : specifies eSDHC base clock frequency. > - > Optional properties: > - sdhci,wp-inverted : specifies that eSDHC controller reports > inverted write-protect state; New devices should use the generic > -- > 1.9.1 > > _______________________________________________ > linux-devel mailing list > linux-devel@xxxxxxxxxxxxxxxxxxxx > http://gforge.freescale.net/mailman/listinfo/linux-devel -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
