On 26.07.2018 14:19, Aapo Vienamo wrote: > Add a property to mark controllers which operate at a 1.8 V fixed I/O > voltage. > > This feature of the hardware needs to be signaled this way because it > cannot be probed at runtime or reliably derived from other properties. Is this really needed? Can we not use vqmmc to determine which voltage the controller runs on? There is already some precedence in the SDHCI core to determine which voltage levels are supported: https://lkml.org/lkml/2018/7/5/342 -- Stefan > > Signed-off-by: Aapo Vienamo <avienamo@xxxxxxxxxx> > --- > Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git > a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt > b/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt > index 90c214d..95010cf 100644 > --- a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt > +++ b/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt > @@ -45,6 +45,8 @@ Optional properties for Tegra210 and Tegra186: > for controllers supporting multiple voltage levels. The order of names > should correspond to the pin configuration states in pinctrl-0 and > pinctrl-1. > +- nvidia,only-1-8-v : The presence of this property indicates that the > + controller operates at a 1.8 V fixed I/O voltage. > > Example: > sdhci@700b0000 { -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
