summaryrefslogtreecommitdiff
path: root/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2022-04-25 14:47:07 +0300
committerArnd Bergmann <arnd@arndb.de>2022-04-25 14:49:01 +0300
commit2f477ee3ed92d7b3786778399cf3e08007721c0f (patch)
tree34aef174372c99d6a8ab835a777e857b10aa4b26 /arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
parent846e24dcae5d5d513408b66f7853a93ab2280735 (diff)
downloadlinux-2f477ee3ed92d7b3786778399cf3e08007721c0f.tar.xz
Revert "arm64: dts: tegra: Fix boolean properties with values"
This reverts commit 1a67653de0dd, which caused a boot regression. The behavior of the "drive-push-pull" in the kernel does not match what the binding document describes. Revert Rob's patch to make the DT match the kernel again, rather than the binding. Link: https://lore.kernel.org/lkml/YlVAy95eF%2F9b1nmu@orome/ Reported-by: Thierry Reding <thierry.reding@gmail.com> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi')
-rw-r--r--arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi6
1 files changed, 3 insertions, 3 deletions
diff --git a/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi b/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
index 0fe772b04bd0..75eb743a7242 100644
--- a/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra210-p2180.dtsi
@@ -59,7 +59,7 @@
gpio1 {
pins = "gpio1";
function = "fps-out";
- drive-push-pull;
+ drive-push-pull = <1>;
maxim,active-fps-source = <MAX77620_FPS_SRC_0>;
maxim,active-fps-power-up-slot = <7>;
maxim,active-fps-power-down-slot = <0>;
@@ -68,7 +68,7 @@
gpio2_3 {
pins = "gpio2", "gpio3";
function = "fps-out";
- drive-open-drain;
+ drive-open-drain = <1>;
maxim,active-fps-source = <MAX77620_FPS_SRC_0>;
};
@@ -80,7 +80,7 @@
gpio5_6_7 {
pins = "gpio5", "gpio6", "gpio7";
function = "gpio";
- drive-push-pull;
+ drive-push-pull = <1>;
};
};