From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
Doug Zobel <douglas.zobel@climate.com>,
Michael Polyntsov <michael.polyntsov@iopsys.eu>,
Mikhail Kshevetskiy <mikhail.kshevetskiy@iopsys.eu>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Subject: [PATCH 10/27] led: Drop LED_STATUS from Kconfig
Date: Thu, 26 Sep 2024 22:44:30 +0200 [thread overview]
Message-ID: <20240926204455.963584-11-sjg@chromium.org> (raw)
In-Reply-To: <20240926204455.963584-1-sjg@chromium.org>
Drop all of these configs, which are now unused.
Signed-off-by: Simon Glass <sjg@chromium.org>
---
drivers/led/Kconfig | 316 --------------------------------------------
1 file changed, 316 deletions(-)
diff --git a/drivers/led/Kconfig b/drivers/led/Kconfig
index 32f0eade710..f4d47d0f327 100644
--- a/drivers/led/Kconfig
+++ b/drivers/led/Kconfig
@@ -114,320 +114,4 @@ config SPL_LED_GPIO
endif # LED
-config LED_STATUS
- bool "Enable status LED API"
- help
- Allows common u-boot commands to use a board's leds to
- provide status for activities like booting and downloading files.
-
-if LED_STATUS
-
-# Hidden constants
-
-config LED_STATUS_OFF
- int
- default 0
-
-config LED_STATUS_BLINKING
- int
- default 1
-
-config LED_STATUS_ON
- int
- default 2
-
-# Hidden constants end
-
-config LED_STATUS_GPIO
- bool "GPIO status LED implementation"
- help
- The status LED can be connected to a GPIO pin. In such cases, the
- gpio_led driver can be used as a status LED backend implementation.
-
-comment "LEDs parameters"
-
-config LED_STATUS0
- bool "Enable status LED 0"
-
-if LED_STATUS0
-
-config LED_STATUS_BIT
- int "identification"
- help
- CONFIG_LED_STATUS_BIT is passed into the __led_* functions to identify
- which LED is being acted on. As such, the chosen value must be unique
- with respect to the other CONFIG_LED_STATUS_BIT's. Mapping the value
- to a physical LED is the responsibility of the __led_* function.
-
-config LED_STATUS_STATE
- int "initial state"
- range LED_STATUS_OFF LED_STATUS_ON
- default LED_STATUS_OFF
- help
- Should be set one of the following:
- 0 - off
- 1 - blinking
- 2 - on
-
-config LED_STATUS_FREQ
- int "blink frequency"
- range 2 10
- default 2
- help
- The LED blink period calculated from LED_STATUS_FREQ:
- LED_STATUS_PERIOD = CONFIG_SYS_HZ/LED_STATUS_FREQ
- Values range: 2 - 10
-
-endif # LED_STATUS0
-
-config LED_STATUS1
- bool "Enable status LED 1"
-
-if LED_STATUS1
-
-config LED_STATUS_BIT1
- int "identification"
- help
- CONFIG_LED_STATUS_BIT1 is passed into the __led_* functions to
- identify which LED is being acted on. As such, the chosen value must
- be unique with respect to the other CONFIG_LED_STATUS_BIT's. Mapping
- the value to a physical LED is the responsibility of the __led_*
- function.
-
-config LED_STATUS_STATE1
- int "initial state"
- range LED_STATUS_OFF LED_STATUS_ON
- default LED_STATUS_OFF
- help
- Should be set one of the following:
- 0 - off
- 1 - blinking
- 2 - on
-
-config LED_STATUS_FREQ1
- int "blink frequency"
- range 2 10
- default 2
- help
- The LED blink period calculated from LED_STATUS_FREQ1:
- LED_STATUS_PERIOD1 = CONFIG_SYS_HZ/LED_STATUS_FREQ1
- Values range: 2 - 10
-
-endif # LED_STATUS1
-
-config LED_STATUS2
- bool "Enable status LED 2"
-
-if LED_STATUS2
-
-config LED_STATUS_BIT2
- int "identification"
- help
- CONFIG_LED_STATUS_BIT2 is passed into the __led_* functions to
- identify which LED is being acted on. As such, the chosen value must
- be unique with respect to the other CONFIG_LED_STATUS_BIT's. Mapping
- the value to a physical LED is the responsibility of the __led_*
- function.
-
-config LED_STATUS_STATE2
- int "initial state"
- range LED_STATUS_OFF LED_STATUS_ON
- default LED_STATUS_OFF
- help
- Should be set one of the following:
- 0 - off
- 1 - blinking
- 2 - on
-
-config LED_STATUS_FREQ2
- int "blink frequency"
- range 2 10
- default 2
- help
- The LED blink period calculated from LED_STATUS_FREQ2:
- LED_STATUS_PERIOD2 = CONFIG_SYS_HZ/LED_STATUS_FREQ2
- Values range: 2 - 10
-
-endif # LED_STATUS2
-
-config LED_STATUS3
- bool "Enable status LED 3"
-
-if LED_STATUS3
-
-config LED_STATUS_BIT3
- int "identification"
- help
- CONFIG_LED_STATUS_BIT3 is passed into the __led_* functions to
- identify which LED is being acted on. As such, the chosen value must
- be unique with respect to the other CONFIG_LED_STATUS_BIT's. Mapping
- the value to a physical LED is the responsibility of the __led_*
- function.
-
-config LED_STATUS_STATE3
- int "initial state"
- range LED_STATUS_OFF LED_STATUS_ON
- default LED_STATUS_OFF
- help
- Should be set one of the following:
- 0 - off
- 1 - blinking
- 2 - on
-
-config LED_STATUS_FREQ3
- int "blink frequency"
- range 2 10
- default 2
- help
- The LED blink period calculated from LED_STATUS_FREQ3:
- LED_STATUS_PERIOD3 = CONFIG_SYS_HZ/LED_STATUS_FREQ3
- Values range: 2 - 10
-
-endif # LED_STATUS3
-
-config LED_STATUS4
- bool "Enable status LED 4"
-
-if LED_STATUS4
-
-config LED_STATUS_BIT4
- int "identification"
- help
- CONFIG_LED_STATUS_BIT4 is passed into the __led_* functions to
- identify which LED is being acted on. As such, the chosen value must
- be unique with respect to the other CONFIG_LED_STATUS_BIT's. Mapping
- the value to a physical LED is the responsibility of the __led_*
- function.
-
-config LED_STATUS_STATE4
- int "initial state"
- range LED_STATUS_OFF LED_STATUS_ON
- default LED_STATUS_OFF
- help
- Should be set one of the following:
- 0 - off
- 1 - blinking
- 2 - on
-
-config LED_STATUS_FREQ4
- int "blink frequency"
- range 2 10
- default 2
- help
- The LED blink period calculated from LED_STATUS_FREQ4:
- LED_STATUS_PERIOD4 = CONFIG_SYS_HZ/LED_STATUS_FREQ4
- Values range: 2 - 10
-
-endif # LED_STATUS4
-
-config LED_STATUS5
- bool "Enable status LED 5"
-
-if LED_STATUS5
-
-config LED_STATUS_BIT5
- int "identification"
- help
- CONFIG_LED_STATUS_BIT5 is passed into the __led_* functions to
- identify which LED is being acted on. As such, the chosen value must
- be unique with respect to the other CONFIG_LED_STATUS_BIT's. Mapping
- the value to a physical LED is the responsibility of the __led_*
- function.
-
-config LED_STATUS_STATE5
- int "initial state"
- range LED_STATUS_OFF LED_STATUS_ON
- default LED_STATUS_OFF
- help
- Should be set one of the following:
- 0 - off
- 1 - blinking
- 2 - on
-
-config LED_STATUS_FREQ5
- int "blink frequency"
- range 2 10
- default 2
- help
- The LED blink period calculated from LED_STATUS_FREQ5:
- LED_STATUS_PERIOD5 = CONFIG_SYS_HZ/LED_STATUS_FREQ5
- Values range: 2 - 10
-
-endif # LED_STATUS5
-
-config LED_STATUS_BOOT_ENABLE
- bool "Enable BOOT LED"
- help
- Enable to turn an LED on when the board is booting.
-
-if LED_STATUS_BOOT_ENABLE
-
-config LED_STATUS_BOOT
- int "LED to light when the board is booting"
- help
- Valid enabled LED device number.
-
-endif # LED_STATUS_BOOT_ENABLE
-
-config LED_STATUS_RED_ENABLE
- bool "Enable red LED"
- help
- Enable red status LED.
-
-if LED_STATUS_RED_ENABLE
-
-config LED_STATUS_RED
- int "Red LED identification"
- help
- Valid enabled LED device number.
-
-endif # LED_STATUS_RED_ENABLE
-
-config LED_STATUS_YELLOW_ENABLE
- bool "Enable yellow LED"
- help
- Enable yellow status LED.
-
-if LED_STATUS_YELLOW_ENABLE
-
-config LED_STATUS_YELLOW
- int "Yellow LED identification"
- help
- Valid enabled LED device number.
-
-endif # LED_STATUS_YELLOW_ENABLE
-
-config LED_STATUS_BLUE_ENABLE
- bool "Enable blue LED"
- help
- Enable blue status LED.
-
-if LED_STATUS_BLUE_ENABLE
-
-config LED_STATUS_BLUE
- int "Blue LED identification"
- help
- Valid enabled LED device number.
-
-endif # LED_STATUS_BLUE_ENABLE
-
-config LED_STATUS_GREEN_ENABLE
- bool "Enable green LED"
- help
- Enable green status LED.
-
-if LED_STATUS_GREEN_ENABLE
-
-config LED_STATUS_GREEN
- int "Green LED identification"
- help
- Valid enabled LED device number (0-5).
-
-endif # LED_STATUS_GREEN_ENABLE
-
-config LED_STATUS_CMD
- bool "Enable status LED commands"
-
-endif # LED_STATUS
-
endmenu
--
2.43.0
next prev parent reply other threads:[~2024-09-26 20:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 20:44 [PATCH 00/27] led: Remove old status-LED code Simon Glass
2024-09-26 20:44 ` [PATCH 01/27] led: Drop LED_STATUS_BOARD_SPECIFIC Simon Glass
2024-09-26 20:44 ` [PATCH 02/27] arm: Drop old LED support Simon Glass
2024-09-26 20:44 ` [PATCH 03/27] common: doc: " Simon Glass
2024-09-26 20:44 ` [PATCH 04/27] st: stm32f429: Drop old LED code Simon Glass
2024-09-26 20:44 ` [PATCH 05/27] led: Make the LED config common Simon Glass
2024-09-26 20:44 ` [PATCH 06/27] eb_cpu5282: Drop STATUS_LED Simon Glass
2024-09-26 20:44 ` [PATCH 07/27] mx23_olinuxino: " Simon Glass
2024-09-26 20:44 ` [PATCH 08/27] pinephone: " Simon Glass
2024-09-26 20:44 ` [PATCH 09/27] socfpga_vining_fpga: " Simon Glass
2024-09-26 20:44 ` Simon Glass [this message]
2024-09-26 20:44 ` [PATCH 11/27] led: Drop the legacy LED command Simon Glass
2024-09-26 20:44 ` [PATCH 12/27] misc: Drop gpio_led driver Simon Glass
2024-09-26 20:44 ` [PATCH 13/27] pca9551_led: Delete driver Simon Glass
2024-09-26 20:44 ` [PATCH 14/27] misc: status_led: " Simon Glass
2024-09-26 20:44 ` [PATCH 15/27] m68k: Drop unused status_led.h header file Simon Glass
2024-10-01 7:21 ` Acked Angelo Dureghello
2024-09-26 20:44 ` [PATCH 16/27] powerpc: Drop status-LED code Simon Glass
2024-09-26 20:44 ` [PATCH 17/27] eb_cpu5282: " Simon Glass
2024-09-26 20:44 ` [PATCH 18/27] igep00x0: Drop unused status_led.h header file Simon Glass
2024-09-26 21:30 ` Javier Martinez Canillas
2024-09-26 20:44 ` [PATCH 19/27] mx23_olinuxino: Drop status-LED code Simon Glass
2024-09-26 21:39 ` Marek Vasut
2024-09-26 22:10 ` Simon Glass
2024-09-26 22:19 ` Marek Vasut
2024-09-27 10:43 ` Simon Glass
2024-09-27 10:51 ` Marek Vasut
2024-09-26 20:44 ` [PATCH 20/27] vining_fpga: " Simon Glass
2024-09-26 20:44 ` [PATCH 21/27] sunxi: " Simon Glass
2024-09-26 20:44 ` [PATCH 22/27] common: Drop status-LED code in board_r Simon Glass
2024-09-26 20:44 ` [PATCH 23/27] image: Drop unused status_led.h header file Simon Glass
2024-09-26 20:44 ` [PATCH 24/27] ide: " Simon Glass
2024-09-26 20:44 ` [PATCH 25/27] mpc83xx: Drop status-LED code Simon Glass
2024-09-26 20:44 ` [PATCH 26/27] net: " Simon Glass
2024-09-26 20:44 ` [PATCH 27/27] led: Drop status_led header file Simon Glass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240926204455.963584-11-sjg@chromium.org \
--to=sjg@chromium.org \
--cc=douglas.zobel@climate.com \
--cc=michael.polyntsov@iopsys.eu \
--cc=mikhail.kshevetskiy@iopsys.eu \
--cc=rasmus.villemoes@prevas.dk \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox