summaryrefslogtreecommitdiff
path: root/include/status_led.h
diff options
context:
space:
mode:
authorBernhard Nortmann <bernhard.nortmann@web.de>2015-08-21 15:13:21 +0200
committerTom Rini <trini@konsulko.com>2015-10-24 13:50:02 -0400
commit13cfbe51357bf3275b14046e0031ea2b7fdaf8ce (patch)
tree6b2432f23b0ad1f8941b56157a3d9a6d693f9542 /include/status_led.h
parentd375ebbcb655ce8f9012cf93db347d3ced66eaac (diff)
downloadu-boot-13cfbe51357bf3275b14046e0031ea2b7fdaf8ce.tar.gz
allow LED initialization without STATUS_LED_BOOT
For current U-Boot to initialize status LEDs via status_led_init(), it is required to have both CONFIG_STATUS_LED and STATUS_LED_BOOT defined. This may be a particular concern with GPIO LEDs, where __led_init() is required to correctly set up the GPIO (gpio_request and gpio_direction_output). Without STATUS_LED_BOOT the initialization isn't called, which could leave the user with a non-functional "led" command - due to the fact that the LED routines in gpio_led.c use gpio_set_value() just fine, but the GPIO never got set up properly in the first place. I think having CONFIG_STATUS_LED is sufficient to justify a corresponding call to status_led_init(), even with no STATUS_LED_BOOT defined. To do so, common/board_r.c needs call that routine, so it now is exposed via status_led.h. Signed-off-by: Bernhard Nortmann <bernhard.nortmann@web.de> [trini: Add dummy __led_init to pca9551_led.c] Signed-off-by: Tom Rini <trini@konsulko.com>
Diffstat (limited to 'include/status_led.h')
-rw-r--r--include/status_led.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/status_led.h b/include/status_led.h
index f6be18146b..396ea882ea 100644
--- a/include/status_led.h
+++ b/include/status_led.h
@@ -23,6 +23,7 @@
#define STATUS_LED_BLINKING 1
#define STATUS_LED_ON 2
+void status_led_init(void);
void status_led_tick (unsigned long timestamp);
void status_led_set (int led, int state);