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/stm32mp157c-ed1-u-boot.dtsi | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/arch/arm/dts/stm32mp157c-ed1-u-boot.dtsi b/arch/arm/dts/stm32mp157c-ed1-u-boot.dtsi index d93359f967c..e44ea84b88f 100644 --- a/arch/arm/dts/stm32mp157c-ed1-u-boot.dtsi +++ b/arch/arm/dts/stm32mp157c-ed1-u-boot.dtsi @@ -14,8 +14,6 @@ }; config { - u-boot,boot-led = "led-blue"; - u-boot,error-led = "led-red"; u-boot,mmc-env-partition = "fip"; }; @@ -61,7 +59,7 @@ led { compatible = "gpio-leds"; - led-blue { + led_blue: led-blue { gpios = <&gpiod 9 GPIO_ACTIVE_HIGH>; }; @@ -69,6 +67,12 @@ gpios = <&gpioa 13 GPIO_ACTIVE_LOW>; }; }; + + options { + u-boot { + boot-led = <&led_blue>; + }; + }; }; &clk_hse { -- 2.43.0
