Hi, On Wed, Jun 8, 2016 at 1:20 AM, Shawn Lin <shawn.lin@xxxxxxxxxxxxxx> wrote: > Let's add some basic description for cap-no-sdio, > cap-no-sd and cap-no-mmc. > > Signed-off-by: Shawn Lin <shawn.lin@xxxxxxxxxxxxxx> > > --- > > Documentation/devicetree/bindings/mmc/mmc.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mmc/mmc.txt b/Documentation/devicetree/bindings/mmc/mmc.txt > index ecc007a..e16d42b 100644 > --- a/Documentation/devicetree/bindings/mmc/mmc.txt > +++ b/Documentation/devicetree/bindings/mmc/mmc.txt > @@ -39,6 +39,9 @@ Optional properties: > - cap-power-off-card: powering off the card is safe > - cap-mmc-hw-reset: eMMC hardware reset is supported > - cap-sdio-irq: enable SDIO IRQ signalling on this interface > +- cap-no-sdio: skip sending sdio cmd during initialization > +- cap-no-sd: skip sending sd cmd during initialization > +- cap-no-mmc: skip sending mmc cmd during initialization In the past it has been determined that the "cap-" prefix is unnecessary. Some properties still have "cap-" because of backward compatibility reasons, but as I understand it new properties shouldn't start with "cap-". See <https://lists.ozlabs.org/pipermail/devicetree-discuss/2013-June/034664.html> for reference. -Doug -- 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
