summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/meson8m2.dtsi
diff options
context:
space:
mode:
authorJerome Brunet <jbrunet@baylibre.com>2018-11-09 17:04:45 +0300
committerKevin Hilman <khilman@baylibre.com>2018-11-29 03:41:11 +0300
commit7e26335b1a3fb2400fcf6d5eb35328257ea2e139 (patch)
tree1cda79f89edb32f06334e25a0e7b0f0ea0aa7cf6 /arch/arm/boot/dts/meson8m2.dtsi
parent340cda67ed80d976c6bec143979cb34bef4c9c85 (diff)
downloadlinux-7e26335b1a3fb2400fcf6d5eb35328257ea2e139.tar.xz
ARM: dts: meson: consistently disable pin bias
On Amlogic chipsets, the bias set through pinconf applies to the pad itself, not only the GPIO function. This means that even when we change the function of the pad from GPIO to anything else, the bias previously set still applies. As we have seen with the eMMC, depending on the bias type and the function, it may trigger problems. The underlying issue is that we inherit whatever was left by previous user of the pad (pinconf, u-boot or the ROM code). As a consequence, the actual setup we will get is undefined. There is nothing mentioned in the documentation about pad bias and pinmux function, however leaving it undefined is not an option. This change consistently disable the pad bias for every pinmux functions. It seems to work well, we can only assume that the necessary bias (if any) is already provided by the pin function itself. Signed-off-by: Jerome Brunet <jbrunet@baylibre.com> Acked-by: Martin Blumenstingl<martin.blumenstingl@googlemail.com> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
Diffstat (limited to 'arch/arm/boot/dts/meson8m2.dtsi')
-rw-r--r--arch/arm/boot/dts/meson8m2.dtsi1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm/boot/dts/meson8m2.dtsi b/arch/arm/boot/dts/meson8m2.dtsi
index 3e1f92273d7b..d1a28c2adac5 100644
--- a/arch/arm/boot/dts/meson8m2.dtsi
+++ b/arch/arm/boot/dts/meson8m2.dtsi
@@ -45,6 +45,7 @@
"eth_rxd1", "eth_rxd0",
"eth_mdio", "eth_mdc";
function = "ethernet";
+ bias-disable;
};
};
};