Remove u-boot,error-led property as it's the legacy LED stuff. Use /options/u-boot to configure LED device as described here [1].
[1] https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/options/u-boot.yaml Signed-off-by: Patrice Chotard <[email protected]> --- arch/arm/dts/stm32mp135f-dk-u-boot.dtsi | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/arch/arm/dts/stm32mp135f-dk-u-boot.dtsi b/arch/arm/dts/stm32mp135f-dk-u-boot.dtsi index f004e9840a2..a9c575319c5 100644 --- a/arch/arm/dts/stm32mp135f-dk-u-boot.dtsi +++ b/arch/arm/dts/stm32mp135f-dk-u-boot.dtsi @@ -11,11 +11,16 @@ }; config { - u-boot,boot-led = "led-blue"; - u-boot,error-led = "led-red"; u-boot,mmc-env-partition = "u-boot-env"; }; + options { + u-boot { + compatible = "u-boot,config"; + boot-led = <&led_blue>; + }; + }; + gpio-keys { button-user-1 { label = "User-1"; @@ -30,7 +35,7 @@ }; leds { - led-blue { + led_blue: led-blue { /delete-property/default-state; }; -- 2.43.0
