aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichal Simek <michal.simek@amd.com>2024-01-10 13:34:20 +0100
committerMichal Simek <michal.simek@amd.com>2024-01-11 14:16:34 +0100
commit64a31fe710708cd21f1ccb36b369b8d8178d3f0a (patch)
tree081e1f1ef19ed86c3a0a4aff3cd611eb564467a2
parentc9190693b052036cf9fac5f48d80f24d06a268fc (diff)
arm64: zynqmp: Remove ltc2954 node
Remove already disabled node. GPIO connections are handled by pmufw that's why there is no reason to have it described for non secure firmware. If someone wants to handle it from OS revert this patch and also update PMUFW configuration and pinctrl setting for these GPIO pins. Link: https://lore.kernel.org/r/f26b1a780ec44444d62e2dd696a05e2a37fa0993.1704890056.git.michal.simek@amd.com Signed-off-by: Michal Simek <michal.simek@amd.com>
-rw-r--r--arch/arm/dts/zynqmp-zcu100-revC.dts9
1 files changed, 0 insertions, 9 deletions
diff --git a/arch/arm/dts/zynqmp-zcu100-revC.dts b/arch/arm/dts/zynqmp-zcu100-revC.dts
index 49d5cdbba5..c5945067cd 100644
--- a/arch/arm/dts/zynqmp-zcu100-revC.dts
+++ b/arch/arm/dts/zynqmp-zcu100-revC.dts
@@ -103,15 +103,6 @@
};
};
- ltc2954: ltc2954 { /* U7 */
- compatible = "lltc,ltc2954", "lltc,ltc2952";
- status = "disabled";
- trigger-gpios = <&gpio 26 GPIO_ACTIVE_LOW>; /* INT line - input */
- /* If there is HW watchdog on mezzanine this signal should be connected there */
- watchdog-gpios = <&gpio 35 GPIO_ACTIVE_HIGH>; /* MIO on PAD */
- kill-gpios = <&gpio 34 GPIO_ACTIVE_LOW>; /* KILL signal - output */
- };
-
wmmcsdio_fixed: fixedregulator-mmcsdio {
compatible = "regulator-fixed";
regulator-name = "wmmcsdio_fixed";