From: Patrice Chotard <patrice.chotard@foss.st.com>
Date: Tue, 9 Apr 2024 15:01:58 +0000 (+0200)
Subject: ARM: dts: stm32: Don't probe led-red/led-blue at boot for stm32mp135f-dk-u-boot
X-Git-Url: http://git.dujemihanovic.xyz/html/static/%7B%7B%20.Permalink%20%7D%7D?a=commitdiff_plain;h=1e26c20662e9a7483e64d609aab286235fe13a3b;p=u-boot.git

ARM: dts: stm32: Don't probe led-red/led-blue at boot for stm32mp135f-dk-u-boot

led-red and button dedicated to fastboot share the same gpio GPIOA13.
led-blue and button dedicated to stm32prog share the same gpio GPIOA14.
Led driver is probed early so the corresponding gpio is taken and
configured in output which forbid fastboot and stm32prog button usage.

To avoid this, remove the "default-state" property from led-red and
led-blue led's node.

This will avoid to trigger the led driver probe() to configure the led
default state during startup.

Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
Reviewed-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
---

diff --git a/arch/arm/dts/stm32mp135f-dk-u-boot.dtsi b/arch/arm/dts/stm32mp135f-dk-u-boot.dtsi
index e64ded1346..8f42735609 100644
--- a/arch/arm/dts/stm32mp135f-dk-u-boot.dtsi
+++ b/arch/arm/dts/stm32mp135f-dk-u-boot.dtsi
@@ -30,10 +30,13 @@
 	};
 
 	leds {
+		led-blue {
+			/delete-property/default-state;
+		};
+
 		led-red {
 			color = <LED_COLOR_ID_RED>;
 			gpios = <&gpioa 13 GPIO_ACTIVE_LOW>;
-			default-state = "off";
 		};
 	};
 };