On Wed, Nov 19, 2025 at 06:27:27PM +0100, Quentin Schulz wrote: > From: Quentin Schulz <[email protected]> > > 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]>
Applied to u-boot/next, thanks! -- Tom
signature.asc
Description: PGP signature
