summaryrefslogtreecommitdiffstats
path: root/drivers/leds/trigger
diff options
context:
space:
mode:
authorGeert Uytterhoeven <geert@linux-m68k.org>2015-05-05 18:32:25 +0200
committerJacek Anaszewski <j.anaszewski@samsung.com>2015-08-28 14:05:57 +0200
commit823227419588001f2d4accf3c5660cd99442a0f8 (patch)
treec604a7baa786af4636de0f7945377554e83445ee /drivers/leds/trigger
parentaa14318aa02f14044acf81f418e1a1cbda29fcfc (diff)
downloadblackbird-obmc-linux-823227419588001f2d4accf3c5660cd99442a0f8.tar.gz
blackbird-obmc-linux-823227419588001f2d4accf3c5660cd99442a0f8.zip
leds: Allow compile test of GPIO consumers if !GPIOLIB
The GPIO subsystem provides dummy GPIO consumer functions if GPIOLIB is not enabled. Hence drivers that depend on GPIOLIB, but use GPIO consumer functionality only, can still be compiled if GPIOLIB is not enabled. Relax the dependency on GPIOLIB if COMPILE_TEST is enabled, where appropriate. Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Richard Purdie <rpurdie@rpsys.net> Cc: linux-leds@vger.kernel.org Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
Diffstat (limited to 'drivers/leds/trigger')
-rw-r--r--drivers/leds/trigger/Kconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/leds/trigger/Kconfig b/drivers/leds/trigger/Kconfig
index 49794b47b51c..5bda6a9b56bb 100644
--- a/drivers/leds/trigger/Kconfig
+++ b/drivers/leds/trigger/Kconfig
@@ -72,7 +72,7 @@ config LEDS_TRIGGER_CPU
config LEDS_TRIGGER_GPIO
tristate "LED GPIO Trigger"
depends on LEDS_TRIGGERS
- depends on GPIOLIB
+ depends on GPIOLIB || COMPILE_TEST
help
This allows LEDs to be controlled by gpio events. It's good
when using gpios as switches and triggering the needed LEDs
OpenPOWER on IntegriCloud