michael/u-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

led: remove support for red LED in legacy API

Browse Source 
To the exception of red_led_on in the arm-specific assembly code, all
code interacting with the red status LED was guarded by the
CONFIG_LED_STATUS_RED symbol, which is enabled in none of the upstream
defconfigs.

Since the last board which overrode the weak red_led_on function got
migrated to the new LED mechanism, there's also no user of the
arm-specific assembly code anymore, therefore it can be removed along
the other unreachable code sections.

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
Reviewed-by: Heiko Schocher <hs@nabladev.com>
This commit is contained in:
Quentin Schulz
2025-11-19 18:01:15 +01:00
committed by Tom Rini
parent b06e52f2ea
commit c4594242aa
7 changed files with 0 additions and 83 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
common/board_f.c
View File

@@ -54,20 +54,6 @@
DECLARE_GLOBAL_DATA_PTR;
/*
* TODO(sjg@chromium.org): IMO this code should be
* refactored to a single function, something like:
*
* void led_set_state(enum led_colour_t colour, int on);
*/
/************************************************************************
* Coloured LED functionality
************************************************************************
* May be supplied by boards if desired
*/
__weak void red_led_on(void) {}
__weak void red_led_off(void) {}
/*
* Why is gd allocated a register? Prior to reloc it might be better to
* just pass it around to each function in this file?