diff options
| author | Quentin Schulz <[email protected]> | 2025-11-19 18:27:27 +0100 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2025-12-16 11:38:58 -0600 |
| commit | 417254ff08ef6647fd73c6963c95ba06015699df (patch) | |
| tree | 711e36d3f05a77b9682b3b2a6c247147bf4ad6c8 /scripts | |
| parent | 3f0528882c0dd9ead93415f140559a44ab1e9885 (diff) | |
board: BuS: remove support for BOOT LED
We are trying to get rid of the legacy LED API and this is one of the
last users.
As far as I understood from the code, only one LED is controllable and
it is a GPIO led. When initializing the LED, it is always enabled
regardless of the passed argument, same for the mask.
In addition, the LED is used as a BOOT LED.
To keep the same behavior, a GPIO driver should be written, then add a
gpio-leds node which makes use of a GPIO from said driver, add the
/options/u-boot/boot-led property pointing at this new GPIO LED node and
then enable CONFIG_LED as well as CONFIG_LED_BOOT. This should result in
the same behavior using the modern framework.
Signed-off-by: Quentin Schulz <[email protected]>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions