diff options
| author | Quentin Schulz <[email protected]> | 2025-11-12 18:48:12 +0100 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2025-12-03 11:03:45 -0600 |
| commit | cf8e0d58cedc38375705ad2cf5c52b0f9bd760f2 (patch) | |
| tree | 2fcb27d97a4aa42febcb2f20dfde8da973e8977e | |
| parent | 7759839fb299c9dea4beb1232dadb3141c7fa8bc (diff) | |
arm: dts: rockchip: rk3399-puma: remove u-boot,boot-led
There's no code to make use of it.
Further more, the HW default state of that LED is on and migrating this
to the LED_BOOT implem brings no benefit as it'll stay on if U-Boot
reaches its main-loop. Blinking the LED_BOOT also doesn't help because
it doesn't blink for long enough to be noticeable before it's kept on.
This is by design, c.f.
https://source.denx.de/u-boot/u-boot/-/blob/v2025.10/include/led.h#L32-34
If we want this LED to be doing something different, it'll need to be
handled by a board file anyway.
Considering it hasn't worked in many years, let's just remove it.
Signed-off-by: Quentin Schulz <[email protected]>
| -rw-r--r-- | arch/arm/dts/rk3399-puma-haikou-u-boot.dtsi | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/arm/dts/rk3399-puma-haikou-u-boot.dtsi b/arch/arm/dts/rk3399-puma-haikou-u-boot.dtsi index 55895d0dd19..76e091be232 100644 --- a/arch/arm/dts/rk3399-puma-haikou-u-boot.dtsi +++ b/arch/arm/dts/rk3399-puma-haikou-u-boot.dtsi @@ -17,7 +17,6 @@ u-boot,spl-payload-offset = <0x80000>; /* @ 512KB */ u-boot,mmc-env-offset = <0x5000>; /* @ 20KB */ u-boot,efi-partition-entries-offset = <0x200000>; /* 2MB */ - u-boot,boot-led = "module_led"; sysreset-gpio = <&gpio1 RK_PA6 GPIO_ACTIVE_HIGH>; }; |