summaryrefslogtreecommitdiff
path: root/common
diff options
context:
space:
mode:
authorQuentin Schulz <[email protected]>2025-11-19 18:01:15 +0100
committerTom Rini <[email protected]>2025-12-05 13:38:09 -0600
commitc4594242aafc3452948a6b57dfbaacdfb4ed0860 (patch)
tree93df78019fee580bc6a1691ac585eb86f5bc83a5 /common
parentb06e52f2ea937077b3ff8296e4a67648138ac897 (diff)
led: remove support for red LED in legacy API
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 <[email protected]> Reviewed-by: Heiko Schocher <[email protected]>
Diffstat (limited to 'common')
-rw-r--r--common/board_f.c14
1 files changed, 0 insertions, 14 deletions
diff --git a/common/board_f.c b/common/board_f.c
index 74571cb6d91..df2b0dc899b 100644
--- a/common/board_f.c
+++ b/common/board_f.c
@@ -55,20 +55,6 @@
DECLARE_GLOBAL_DATA_PTR;
/*
- * TODO([email protected]): 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?
*