aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2022-04-25 13:47:07 +0200
committerArnd Bergmann <arnd@arndb.de>2022-04-25 13:49:01 +0200
commit2f477ee3ed92d7b3786778399cf3e08007721c0f (patch)
tree34aef174372c99d6a8ab835a777e857b10aa4b26 /arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi
parentMerge tag 'omap-for-v5.18/fixes-take2' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into arm/fixes (diff)
downloadlinux-dev-2f477ee3ed92d7b3786778399cf3e08007721c0f.tar.xz
linux-dev-2f477ee3ed92d7b3786778399cf3e08007721c0f.zip
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/tegra186-p3310.dtsi')
-rw-r--r--arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi8
1 files changed, 4 insertions, 4 deletions
diff --git a/arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi b/arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi
index 1df84335925b..aff857df25cf 100644
--- a/arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi
@@ -262,25 +262,25 @@
gpio4 {
pins = "gpio4";
function = "32k-out1";
- drive-push-pull;
+ drive-push-pull = <1>;
};
gpio5 {
pins = "gpio5";
function = "gpio";
- drive-push-pull;
+ drive-push-pull = <0>;
};
gpio6 {
pins = "gpio6";
function = "gpio";
- drive-push-pull;
+ drive-push-pull = <1>;
};
gpio7 {
pins = "gpio7";
function = "gpio";
- drive-push-pull;
+ drive-push-pull = <0>;
};
};