This series is a reworked version of the previous seried: misc: introduce STATUS LED activity function
This series port and expand the legacy concept of LED boot from the legacy Status LED API to new LED API. One thing that many device need is a way to communicate to the user that the device is actually doing something. This is especially useful for recovery steps where an user (for example) insert an USB drive, keep a button pressed and the device autorecover. There is currently no way to signal the user externally that the bootloader is processing/recoverying aside from setting a LED on. A solid LED on is not enough and won't actually signal any kind of progress. Solution is the good old blinking LED but uboot doesn't suggest (and support) interrupts and almost all the LED are usually GPIO LED that doesn't support HW blink. Additional Kconfg are also introduced to set the LED boot and activity. Those are referenced by label. A documentation for old and these new LED API is created. (world tested with the azure pipeline) Changes v2: - Drop GPIO SW implementation - Add fix for new LED SW BLINK Christian Marangi (9): led: turn LED ON on initial SW blink led: implement led_set_state/period_by_label led: implement LED boot API common: board_r: rework BOOT LED handling led: implement LED activity API tftp: implement support for LED activity mtd: implement support for LED activity ubi: implement support for LED activity doc: introduce led.rst documentation cmd/mtd.c | 19 +++++ cmd/ubi.c | 15 +++- common/board_r.c | 25 ++++++- doc/api/index.rst | 1 + doc/api/led.rst | 10 +++ drivers/led/Kconfig | 41 +++++++++++ drivers/led/led-uclass.c | 28 ++++++++ drivers/led/led_sw_blink.c | 5 +- include/led.h | 144 +++++++++++++++++++++++++++++++++++++ net/tftp.c | 7 ++ 10 files changed, 290 insertions(+), 5 deletions(-) create mode 100644 doc/api/led.rst -- 2.45.2
