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 05/27] led: Make the LED config common
Date: Thu, 26 Sep 2024 22:44:25 +0200 [thread overview]
Message-ID: <20240926204455.963584-6-sjg@chromium.org> (raw)
In-Reply-To: <20240926204455.963584-1-sjg@chromium.org>
Use an if...endif construct to avoid needing to make everything depend
on LED. Make SPL_LED depend on LED since that seems reasonable.
Signed-off-by: Simon Glass <sjg@chromium.org>
---
drivers/led/Kconfig | 22 ++++++++++++----------
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/drivers/led/Kconfig b/drivers/led/Kconfig
index 5c401f92080..32f0eade710 100644
--- a/drivers/led/Kconfig
+++ b/drivers/led/Kconfig
@@ -9,9 +9,11 @@ config LED
can provide access to board-specific LEDs. Use of the device tree
for configuration is encouraged.
+if LED
+
config LED_BCM6328
bool "LED Support for BCM6328"
- depends on LED && ARCH_BMIPS
+ depends on ARCH_BMIPS
help
This option enables support for LEDs connected to the BCM6328
LED HW controller accessed via MMIO registers.
@@ -22,7 +24,7 @@ config LED_BCM6328
config LED_BCM6358
bool "LED Support for BCM6358"
- depends on LED && ARCH_BMIPS
+ depends on ARCH_BMIPS
help
This option enables support for LEDs connected to the BCM6358
LED HW controller accessed via MMIO registers.
@@ -30,28 +32,28 @@ config LED_BCM6358
config LED_BCM6753
bool "LED Support for BCM6753"
- depends on LED && BCM6855
+ depends on BCM6855
help
This option enables support for LEDs connected to the BCM6753
HW has blinking and fading capabilities and up to 32 LEDs can be controlled.
config LED_BCM6858
bool "LED Support for BCM6858"
- depends on LED && (BCM6856 || BCM6858 || BCM63158)
+ depends on BCM6856 || BCM6858 || BCM63158
help
This option enables support for LEDs connected to the BCM6858
HW has blinking capabilities and up to 32 LEDs can be controlled.
config LED_CORTINA
bool "LED Support for Cortina Access CAxxxx SoCs"
- depends on LED && (CORTINA_PLATFORM)
+ depends on CORTINA_PLATFORM
help
This option enables support for LEDs connected to the Cortina
Access CAxxxx SOCs.
config LED_LP5562
bool "LED Support for LP5562"
- depends on LED && DM_I2C
+ depends on DM_I2C
help
This option enables support for LEDs connected to the TI LP5562
4 channel I2C LED controller. Driver fully supports blink on the
@@ -59,14 +61,13 @@ config LED_LP5562
config LED_PWM
bool "LED PWM"
- depends on LED && DM_PWM
+ depends on DM_PWM
help
Enable support for LEDs connected to PWM.
Linux compatible ofdata.
config LED_BLINK
bool "Support hardware LED blinking"
- depends on LED
help
Some drivers can support automatic blinking of LEDs with a given
period, without needing timers or extra code to handle the timing.
@@ -75,7 +76,6 @@ config LED_BLINK
config LED_SW_BLINK
bool "Support software LED blinking"
- depends on LED
select CYCLIC
help
Turns on led blinking implemented in the software, useful when
@@ -98,7 +98,7 @@ config SPL_LED
config LED_GPIO
bool "LED support for GPIO-connected LEDs"
- depends on LED && DM_GPIO
+ depends on DM_GPIO
help
Enable support for LEDs which are connected to GPIO lines. These
GPIOs may be on the SoC or some other device which provides GPIOs.
@@ -112,6 +112,8 @@ config SPL_LED_GPIO
This option is an SPL-variant of the LED_GPIO option.
See the help of LED_GPIO for details.
+endif # LED
+
config LED_STATUS
bool "Enable status LED API"
help
--
2.43.0
next prev parent reply other threads:[~2024-09-26 20:48 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 ` Simon Glass [this message]
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 ` [PATCH 10/27] led: Drop LED_STATUS from Kconfig Simon Glass
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-6-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