summaryrefslogtreecommitdiff
path: root/drivers/led/Kconfig
diff options
context:
space:
mode:
authorChristian Marangi <[email protected]>2024-10-01 14:24:38 +0200
committerTom Rini <[email protected]>2024-10-10 16:02:20 -0600
commitaad8cfa3ca4b1bb18c4a55d2bbee4f58d3095d64 (patch)
tree2a9f00dc48586d39d6cd9dde0da623d88adea60e /drivers/led/Kconfig
parentfc55ae03fdda244b74756c9dedb16143dbe002bd (diff)
led: implement LED activity API
Implement LED activity API similar to BOOT LED API. Usual activity might be a file transfer with TFTP, a flash write... User of this API will call led_activity_on/off/blink() to signal these kind of activity. New Kconfig is implemented similar to BOOT LED, LED_ACTIVITY to enable support for it. It's introduced a new /options/u-boot property "activity-led" and "activity-led-period" to define the activity LED label and the default period when the activity LED is set to blink mode. If "activity-led-period" is not defined, the value of 250 (ms) is used by default. If CONFIG_LED_BLINK or CONFIG_LED_SW_BLINK is not enabled, led_boot_blink call will fallback to simple LED ON. Signed-off-by: Christian Marangi <[email protected]> Reviewed-by: Simon Glass <[email protected]>
Diffstat (limited to 'drivers/led/Kconfig')
-rw-r--r--drivers/led/Kconfig13
1 files changed, 13 insertions, 0 deletions
diff --git a/drivers/led/Kconfig b/drivers/led/Kconfig
index 59b007a7ef5..c98cbf92fab 100644
--- a/drivers/led/Kconfig
+++ b/drivers/led/Kconfig
@@ -20,6 +20,19 @@ config LED_BOOT
[1] dtschema/schemas/options/u-boot.yaml
+config LED_ACTIVITY
+ bool "Enable LED activity support"
+ help
+ Enable LED activity support.
+
+ LED activity is a specific LED assigned to signal activity operation
+ like file trasnfer, flash write/erase...
+
+ Defined in Device Tree /options/u-boot node. Refer here for the supported
+ options [1].
+
+ [1] dtschema/schemas/options/u-boot.yaml
+
config LED_BCM6328
bool "LED Support for BCM6328"
depends on LED && ARCH_BMIPS