On some systems the sdhci capabilty registers are incorrect for one reason or another. The sdhci-cap-speed-modes-broken property will let the driver know that the sdhci capability registers should not be relied on for speed modes. Instead the driver should check the mmc generic DT bindings. Signed-off-by: Zach Brown <zach.brown@xxxxxx> --- 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 8a37782..671d6c0 100644 --- a/Documentation/devicetree/bindings/mmc/mmc.txt +++ b/Documentation/devicetree/bindings/mmc/mmc.txt @@ -52,6 +52,9 @@ Optional properties: - no-sdio: controller is limited to send sdio cmd during initialization - no-sd: controller is limited to send sd cmd during initialization - no-mmc: controller is limited to send mmc cmd during initialization +- sdhci-cap-speed-modes-broken: One or more of the bits in the sdhci + capabilities registers representing speed modes are incorrect. All the bits + representing speed modes should be ignored. *NOTE* on CD and WP polarity. To use common for all SD/MMC host controllers line polarity properties, we have to fix the meaning of the "normal" and "inverted" -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
