summaryrefslogtreecommitdiff
path: root/board/raspberrypi
diff options
context:
space:
mode:
authorBernhard Nortmann <bernhard.nortmann@web.de>2015-08-21 13:13:21 (GMT)
committerTom Rini <trini@konsulko.com>2015-10-24 17:50:02 (GMT)
commit13cfbe51357bf3275b14046e0031ea2b7fdaf8ce (patch)
tree6b2432f23b0ad1f8941b56157a3d9a6d693f9542 /board/raspberrypi
parentd375ebbcb655ce8f9012cf93db347d3ced66eaac (diff)
downloadu-boot-fsl-qoriq-13cfbe51357bf3275b14046e0031ea2b7fdaf8ce.tar.xz
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 'board/raspberrypi')
0 files changed, 0 insertions, 0 deletions